DOOR Knowledge MCP Server
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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_door_knowledgeA | Busca documentos en la DOOR Knowledge Base por palabras clave, categorías o contenido. Retorna una lista de documentos relevantes con resúmenes. Es MUY RÁPIDO porque usa un índice pre-generado. |
| get_door_documentA | Obtiene el contenido completo de un documento específico de la DOOR Knowledge Base. Usa el ID obtenido de search_door_knowledge. |
| list_door_categoriesB | Lista todas las categorías y subcategorías disponibles en la DOOR Knowledge Base con conteo de documentos. |
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 3 tools
Each tool has a clearly distinct purpose: get_door_document retrieves a specific document by ID, list_door_categories lists categories with counts, and search_door_knowledge searches for documents using keywords or categories. There is no overlap in functionality, making it easy for an agent to select the right tool.
All tool names follow a consistent snake_case pattern with a clear verb_noun structure (get_door_document, list_door_categories, search_door_knowledge). The naming is predictable and enhances readability across the tool set.
With only 3 tools, the server feels thin for a knowledge base domain, as it lacks operations like creating, updating, or deleting documents or categories. While the tools cover basic retrieval and listing, the count is borderline for comprehensive coverage.
The tool surface is significantly incomplete for a knowledge base server. It only supports read operations (get, list, search) with no ability to create, update, or delete documents or categories. This will cause agent failures when full lifecycle management is needed.