Skip to main content
Glama
guillelagoria

DOOR Knowledge MCP Server

get_door_document

Retrieve full content of DOOR Knowledge Base documents using document IDs obtained from search results to access detailed support articles and PDFs.

Instructions

Obtiene el contenido completo de un documento específico de la DOOR Knowledge Base. Usa el ID obtenido de search_door_knowledge.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
document_idYesID del documento (obtenido de search_door_knowledge)

Implementation Reference

  • Registration of the 'get_door_document' tool including name, description, and input schema in the ListToolsRequestHandler.
    {
      name: 'get_door_document',
      description: 'Obtiene el contenido completo de un documento específico de la DOOR Knowledge Base. Usa el ID obtenido de search_door_knowledge.',
      inputSchema: {
        type: 'object',
        properties: {
          document_id: {
            type: 'string',
            description: 'ID del documento (obtenido de search_door_knowledge)',
          },
        },
        required: ['document_id'],
      },
    },
  • Main handler function that loads the search index, finds the document by ID, reads the markdown content from file, and returns formatted response.
    async getDoorDocument(args) {
      const { document_id } = args;
      const index = await this.loadSearchIndex();
    
      // Buscar documento en el índice
      const doc = index.documents.find(d => d.id === document_id);
      if (!doc) {
        throw new Error(`Documento no encontrado: ${document_id}`);
      }
    
      // Leer contenido completo
      const mdPath = path.join(this.knowledgeBasePath, doc.mdPath);
    
      try {
        const content = await fs.readFile(mdPath, 'utf-8');
    
        return {
          content: [
            {
              type: 'text',
              text: `# ${doc.title}\n\n**Categoría:** ${doc.category} > ${doc.subcategory}\n**Páginas:** ${doc.pages}\n**Archivo fuente:** ${doc.sourceFile}\n\n---\n\n${content}`,
            },
          ],
        };
      } catch (err) {
        throw new Error(`No se pudo leer el documento: ${err.message}`);
      }
    }
  • Dispatch case in CallToolRequestHandler that routes to the getDoorDocument method.
    case 'get_door_document':
      return await this.getDoorDocument(request.params.arguments);
Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are provided, so the description carries the full burden. It describes the tool as retrieving full content, which implies a read-only operation, but lacks details on permissions, rate limits, error handling, or output format. The description adds basic context but misses key behavioral traits.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is two concise sentences with zero waste: the first states the purpose, and the second provides usage guidance. It is front-loaded and every sentence earns its place by adding value.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's low complexity (one parameter, no output schema, no annotations), the description is adequate but incomplete. It covers purpose and usage well but lacks details on output format, error cases, or behavioral constraints, which are important for a tool without annotations.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the schema already documents the single parameter 'document_id' with its description. The description adds no additional meaning beyond what the schema provides, such as format examples or constraints, meeting the baseline for high schema coverage.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the specific action ('Obtiene el contenido completo') and resource ('un documento específico de la DOOR Knowledge Base'), distinguishing it from sibling tools like list_door_categories and search_door_knowledge by focusing on retrieving full content of a single document rather than listing categories or searching.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It explicitly states when to use this tool ('Usa el ID obtenido de search_door_knowledge'), providing a clear prerequisite and distinguishing it from the sibling tool search_door_knowledge, which is used to obtain the ID needed here.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/guillelagoria/door-support-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server