​

List Knowledge Bases

​

What it does

• authenticated user
• agentId
• channel
• KB scope
• KB peerScopePolicy

​

Parameters

​

Returns

• knowledgeBases: Array of knowledge base objects with metadata

• id: Unique identifier for the knowledge base
• name: Human-readable name
• description: Brief description of the KB’s purpose
• status: “active” or “archived”
• channel: Channel type (if applicable)
• chunkCount: Number of indexed chunks
• createdAt: Creation timestamp

{
  "knowledgeBases": [
    {
      "id": "kb_abc123",
      "name": "Codebase Documentation",
      "description": "API docs, architecture guides, and README files",
      "status": "active",
      "channel": null,
      "chunkCount": 157,
      "createdAt": 1713302400000
    },
    {
      "id": "kb_def456",
      "name": "Slack #engineering",
      "description": "Engineering channel history and discussions",
      "status": "active",
      "channel": "slack",
      "chunkCount": 2340,
      "createdAt": 1710624000000
    }
  ]
}

​

Examples

​

List all active knowledge bases

crystal_list_knowledge_bases()

​

Include archived knowledge bases

crystal_list_knowledge_bases(includeInactive=true)

​

Filter by channel

crystal_list_knowledge_bases(channel="slack")

​

List all with archival status

crystal_list_knowledge_bases(includeInactive=true, channel="discord")

​

When to use

• Discover available contexts — See what knowledge bases are available before using other KB tools
• Manage knowledge bases — Get a complete inventory of your knowledge bases
• Plan imports — Check what channels/sources are already indexed
• Audit storage — See chunk counts to understand what’s been imported
• Channel-specific queries — Know which KB ID to use for channel-filtered searches

​

Errors

​

Notes

• Knowledge bases can be created via channel imports or manual uploads
• Chunk count indicates the volume of indexed content
• Inactive/archived knowledge bases are hidden by default to reduce clutter
• Channels filter works only on knowledge bases created from those sources
• Each knowledge base has a unique ID used by other KB tools (query, import, etc.)
• Knowledge bases are scoped to the current user or team depending on your setup
• Peer-capable KBs default to strict isolation; cross-chat/shared access on those agents requires peerScopePolicy: "permissive"
• Empty results can mean the KB is inactive, scoped to another agent/channel, hidden by strict peer policy, or outside the caller’s project scope. It does not always mean the row does not exist.
• sourceRole appears on KB metadata when available; use it to choose between canonical references, voice/style corpora, persona guardrails, and client context.