Skip to main content
Glama

Read document

get_document_text
Read-onlyIdempotent

Plain text of an accessible document, in slices of up to 20000 characters. Use next_offset to continue.

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

Input Schema

NameRequiredDescriptionDefault
offsetNoCharacter offset (default 0)
document_idYesDocument id from list_documents
trust_centerYesTrust center id (from list_trust_centers), its domain or the exact company name.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so safety is covered. The description adds genuine value beyond them by disclosing the 20000-character slice size, which sets expectations about partial results. It does not explain truncation behavior or how a caller detects that more text remains.

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 short sentences with zero filler, chunk size front-loaded and continuation advice trailing. Every clause earns its place.

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?

There is no output schema, so the description carries the burden of explaining the return value; it does partially, naming plain text and the slice size. The gap is the continuation contract: the referenced next_offset is nowhere defined, and no way is given to know whether a slice was truncated, so an agent lacks what it needs to page reliably.

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 coverage is 100%, so offset, document_id, and trust_center are already documented, which normally sets a baseline of 3. But the description's only parameter reference is to "next_offset," a field that does not exist in the schema and is not defined by any output schema, which risks an agent inventing an argument rather than reusing offset.

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 resource and output form: "Plain text of an accessible document, in slices of up to 20000 characters." That tells an agent exactly what comes back and distinguishes it from list-style siblings such as list_documents. It stops short of naming which sibling to use instead of this one.

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?

The second sentence gives pagination guidance ("Use next_offset to continue"), which is a real usage instruction for multi-slice reads. However, it never says when to prefer this over search or fetch, nor does it state any prerequisite such as the document being the accessible kind mentioned in the first sentence.

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