Skip to main content
Glama

document_content_get

Read content as json | markdown | html | strings (binary formats: use the REST content endpoint).

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": {
      "document_id": "<document_id>"
    },
    "name": "document_content_get"
  }
}

Input Schema

NameRequiredDescriptionDefault
formatNo
document_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior3/5

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

With no annotations, the description carries the full burden; 'Read' implies non-destructive access, and the binary-format exclusion is a useful behavioral constraint. It says nothing about permissions, size limits, or what happens when format is omitted, so the mutation/safety profile is only partially covered.

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

Conciseness4/5

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

A single front-loaded sentence with zero filler; the pipe-separated format list is terse but scannable. The parenthetical caveat is well placed at the end where it does not bury the primary purpose.

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?

For a two-parameter read tool this is close to adequate, and the format list doubles as a rough return-value description in the absence of an output schema. Missing default-format behavior and document_id semantics keep it from being complete enough to call correctly without trial and error.

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

Parameters2/5

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

Schema description coverage is 0% for both parameters. The description restates the format enum values but adds no meaning about a default format, whether document_id refers to a document or revision, or what 'strings' yields — leaving the only real semantic gap (default behavior) undocumented.

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

Purpose4/5

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

States a specific verb ('Read') and resource ('content') plus the four output formats, so an agent knows exactly what it gets back. It does not explicitly distinguish itself from sibling document_get, leaving the metadata-vs-content split to inference.

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?

Provides a genuine when-not rule: binary formats must go through the REST content endpoint rather than this tool. However, it offers no guidance on when to prefer this over document_get or how format selection should be decided, so the most common ambiguity is unresolved.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources