Skip to main content
Glama
Sign In
mcp-doc-search

mcp-doc-search

by anujmv
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Get document

get_document

Retrieve the full text of a document by its ID to access complete content for citation or deeper reading.

Instructions

Return the full text of a document by its id (filename), for citation or deeper reading.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "id": "<id>"
    },
    "name": "get_document"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesDocument id, e.g. a filename returned by search_docs

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.1/5.0
Behavior3/5

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

No annotations exist, so description carries full burden. It indicates read-only behavior by 'Return the full text' but does not disclose error handling, auth requirements, or rate limits. Minimal behavioral context beyond purpose.

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?

Single sentence efficiently conveys action, subject, and purpose without redundancy. Every word earns its place.

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

Completeness5/5

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

Tool is simple with one parameter and clear purpose. Description covers use case and expected input. No output schema, but return type is implied as 'full text'. Complete for this context.

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 coverage is 100% with description of id as 'Document id, e.g. a filename returned by search_docs'. The tool description adds 'for citation or deeper reading' but no new parameter-specific information beyond the schema. Baseline 3 is appropriate.

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?

Description clearly states verb 'Return' and resource 'full text of a document', specifying the identifier (id as filename) and use case (citation or deeper reading). It distinguishes from sibling search_docs, which is for searching, by focusing on retrieval.

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

Usage Guidelines4/5

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

The phrase 'for citation or deeper reading' implies use after search_docs, but no explicit when-to-use or when-not-to-use guidance is provided. It gives context but lacks exclusions or alternatives.

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

Deploy Server

Other Tools