Knowledge Fabric
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| health_checkA | Check server health and return runtime configuration. Returns embedding provider name and dimension, DB connectivity status, and approximate document/chunk counts. Useful for AI agents to orient themselves before querying. |
| list_sourcesA | List ingested source types and document counts for a tenant. Returns distinct source_type values with document counts so an AI agent can discover what content domains are available before issuing a query. Use source_type as a filter in retrieve_evidence to scope retrieval. Scoped to tenant_id when provided. |
| retrieve_evidenceA | Execute evidence retrieval across indexed content. Parameters:
|
| get_documentD | – |
| explain_retrievalB | Return diagnostic tracing and candidate scoring explanations for a query. Explains candidate counts, per-leg latencies, fusion scores, and degradation status without persisting audit logs. |
| get_index_statusA | Return diagnostic index breakdown: document/chunk counts, sources, and storage status. Scoped to tenant_id when provided. |
| get_evidenceB | Fetch a specific evidence chunk by its integer chunk ID, scoped to tenant. |
| check_consistencyB | Run database consistency audits (detecting orphaned chunks, empty documents, null tenants). |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 8 tools
Most tools have clear boundaries: retrieve_evidence executes search, get_evidence fetches a chunk by ID, get_document likely fetches a full document, and the three diagnostics target different concerns (runtime health, index state, data consistency). Minor ambiguity exists between health_check and get_index_status, and get_document lacks a description, making its boundary with get_evidence less obvious.
The set mostly follows a snake_case verb_noun pattern: list_sources, retrieve_evidence, get_document, explain_retrieval, check_consistency. health_check breaks the pattern slightly (noun-like compound instead of check_health), and get_document/get_evidence/get_index_status share the get_ prefix with different objects, which is predictable.
Eight tools is well-scoped for a knowledge-retrieval and diagnostics server: query, evidence/document access, explainability, health, index status, consistency, and source discovery. Each tool serves a distinct operational need without redundancy.
The retrieval workflow is covered end-to-end: discover sources, retrieve evidence, fetch specific chunks/documents, explain scoring, and inspect health/index/consistency. Minor gaps are the undocumented get_document behavior and the absence of any listing/management operation beyond sources, though ingestion appears to be handled outside this server.