Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.prisme.ai/llms.txt

Use this file to discover all available pages before exploring further.

Capabilities Catalog
The Capabilities Catalog is a centralized registry of tools and capabilities available to AI agents in your organization. It includes MCP servers, functions, file search, skills, guardrails, memory providers, and sub-agents.

Capability Types

TypeDescription
MCPModel Context Protocol servers providing tools via SSE/WebSocket
FunctionCustom HTTP endpoints callable as tools
File SearchKnowledge base search using vector stores
SkillReusable instruction sets for agents
GuardrailInput/output validation and safety filters
MemoryConversation and long-term memory providers
Sub-AgentOther agents that can be invoked as tools

Categories

Organize capabilities into functional categories:
CategoryUse Case
SearchWeb search, document search, RAG
ProductivityCalendar, email, task management
SecurityAuthentication, authorization checks
CompliancePII detection, content filtering
KnowledgeKnowledge bases, documentation
CustomOrganization-specific tools
StoreApp store integrations
GenericGeneral-purpose utilities
ContextContext injection and enrichment

MCP Servers

Model Context Protocol (MCP) servers expose tools to AI agents through a standardized interface.

Adding an MCP Server

  1. Go to Capabilities in the sidebar
  2. Click Add Capability
  3. Select type MCP
  4. Configure:
FieldDescription
Entry NameDisplay name for this server
Server NameIdentifier used in tool calls
SSE/WebSocket URLServer endpoint URL
Auth HeadersAuthentication headers (JSON)
ScopeAccess scope (org, user)
  1. Click Create

Example Configuration

{
  "name": "company-tools",
  "server": "https://mcp.acme.com/sse",
  "headers": {
    "Authorization": "Bearer {{secrets.MCP_TOKEN}}"
  },
  "scope": "org"
}

Functions

Functions are custom HTTP endpoints that agents can call as tools.

Adding a Function

  1. Click Add Capability
  2. Select type Function
  3. Configure:
FieldDescription
Function NameName used in tool calls
DescriptionWhat the function does
Endpoint URLHTTP endpoint to call
ParametersJSON Schema defining input parameters
HTTP HeadersHeaders to include in requests

Example Configuration

{
  "name": "lookup_customer",
  "description": "Look up customer information by ID",
  "url": "https://api.acme.com/customers/lookup",
  "parameters": {
    "type": "object",
    "properties": {
      "customer_id": {
        "type": "string",
        "description": "Customer ID to look up"
      }
    },
    "required": ["customer_id"]
  }
}
Connect vector stores for knowledge base search.
  1. Click Add Capability
  2. Select type File Search
  3. Configure:
FieldDescription
Tool NameUsually knowledge_base
Vector Store IDID of the vector store to search
File search integrates with Knowledges vector stores.

Skills

Skills are reusable instruction sets that modify agent behavior.

Adding a Skill

  1. Click Add Capability
  2. Select type Skill
  3. Configure:
FieldDescription
Skill NameIdentifier for the skill
Short PurposeOne-sentence description
InstructionsDetailed instructions (Markdown)

Example Skill

Name: summarize Purpose: Summarize long documents into key points Instructions:
When asked to summarize content:

1. Read the entire document first
2. Identify the main thesis or purpose
3. Extract 3-5 key points
4. Present as a bulleted list
5. Keep summary under 200 words

Guardrails

Guardrails validate inputs, outputs, or actions to ensure safety and compliance.

Guardrail Types

TypeWhen Applied
InputBefore processing user messages
OutputBefore returning responses to users
ActionBefore executing tool calls

Adding a Guardrail

  1. Click Add Capability
  2. Select type Guardrail
  3. Configure:
FieldDescription
Guardrail NameIdentifier
Guardrail Typeinput, output, or action
DescriptionWhat the guardrail checks
Endpoint URLValidation endpoint

Example Guardrail

{
  "name": "pii_filter",
  "guardrail_type": "output",
  "description": "Detect and redact PII in responses",
  "url": "https://guardrails.acme.com/pii-check"
}

Memory Providers

Memory providers store conversation history and long-term context.

Adding Memory

  1. Click Add Capability
  2. Select type Memory
  3. Configure:
FieldDescription
Memory NameIdentifier
Memory Typeconversation, long_term, etc.
DescriptionWhat this memory stores

Sub-Agents

Sub-agents are other agents that can be invoked as tools, enabling agent composition.

Adding a Sub-Agent

  1. Click Add Capability
  2. Select type Sub-Agent
  3. Configure:
FieldDescription
AgentSelect from published agents
NameOverride display name (optional)
DescriptionWhat this agent does

Built-in vs Custom

Capabilities are marked as:
  • Built-in: Provided by the platform, cannot be edited or deleted
  • Custom: Created by your organization, fully editable
Use the toolbar to find capabilities:
  • Search: Filter by name or description
  • Type: Filter by capability type (MCP, Function, etc.)
  • Category: Filter by functional category

Best Practices

Descriptive Names

Use clear, action-oriented names for tools

Secure Authentication

Store credentials in secrets, reference as {{secrets.KEY}}

Document Parameters

Provide detailed descriptions in JSON Schema

Test Before Deploy

Verify capabilities work before enabling for all agents

Next Steps

Model Governance

Control which models agents can use

Observability

Monitor capability usage and errors