Skip to main content
Glama
Sign In
Doc Manager

Doc Manager

by giuliohome-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Rust
Remote

get_document

Retrieve a single plaintext document by ID. Encrypted documents are refused because their content cannot be read server-side.

Instructions

Fetch a single plaintext document by id. Refuses encrypted documents (their content is unreadable server-side).

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
idYesThe document id (UUID, exactly as returned by list_documents).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4/5.0
Behavior4/5

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

With no annotations, description fully carries behavioral disclosure. It explicitly states that encrypted documents are refused because content is unreadable server-side, a key limitation. However, it does not mention other behaviors like error handling or auth requirements.

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?

Two sentences, zero wasted words. Essential information is front-loaded with purpose first, then a critical behavioral note. Ideal conciseness for an AI agent.

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

Completeness4/5

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

For a simple single-document fetch with one parameter and no output schema, the description covers main functionality and a notable limitation. It could mention output format (plaintext) but that is implied by 'plaintext document'. Minor gap.

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?

Input schema has 100% coverage for the 'id' parameter with description 'The document id (UUID, exactly as returned by list_documents).' The tool description does not add extra parameter info beyond what schema provides, so baseline score of 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 'Fetch a single plaintext document by id.' Verb+resource is specific and unambiguous. It distinguishes from sibling tools like list_documents and search_documents by specifying single document retrieval.

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

Usage Guidelines3/5

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

Description implies usage for fetching a specific document by ID but does not explicitly state when to use vs alternatives or any exclusions. No guidance on prerequisites like obtaining the ID from list_documents.

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