Skip to main content
Glama

Get an agentic-os document

get_document
Read-onlyIdempotent

Fetch the full text of one agentic-os methodology document, named by its exact agentic-os:// URI. Use it to read a document you have already located — normally via search_methodology, whose every result carries the URI to pass here.

Instructions

Fetch the full text of one agentic-os methodology document, named by its exact agentic-os:// URI. Use it to read a document you have already located — normally via search_methodology, whose every result carries the URI to pass here. It resolves exact URIs only and cannot search, so a guessed URI returns an error rather than a near match. Read-only and idempotent: nothing is ever written, and the same URI returns the same document. A body longer than max_chars comes back cut at a code-point boundary with truncated set and total_chars giving the full length.

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": {
      "uri": "<uri>"
    },
    "name": "get_document"
  }
}

Input Schema

NameRequiredDescriptionDefault
uriYesAn agentic-os:// URI, e.g. agentic-os://skills/agentic-sdlc/gate-runner or agentic-os://file/agentic-sdlc/agents/guide-sync.md. Get these from search_methodology.
max_charsNoTruncate the body at this many Unicode code points (not UTF-16 code units — astral-plane characters such as emoji count as one).

Output Schema

NameRequiredDescriptionDefault
uriYesThe requested URI, echoed back unchanged.
textYesThe document body — complete, or cut to max_chars code points when truncated is true.
titleYesThe document's first markdown heading, or its path within the content bundle when it has no heading.
truncatedYestrue when the body was cut because it exceeded max_chars. There is no offset or paging parameter: re-request with a larger max_chars to get the rest.
total_charsYesLength of the complete, untruncated body in Unicode code points — the same unit max_chars is measured in, so total_chars > max_chars is precisely the condition that sets truncated.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.1.8
    • changedInput schema / properties / uri / description
      Previous value: -"An agentic-os:// URI, e.g. agentic-os://skills/agentic-sdlc/qa-gates or agentic-os://file/agentic-sdlc/agents/guide-sync.md. Get these from search_methodology."New value: +"An agentic-os:// URI, e.g. agentic-os://skills/agentic-sdlc/gate-runner or agentic-os://file/agentic-sdlc/agents/guide-sync.md. Get these from search_methodology."
  2. Addedv0.1.6
  3. Removedv0.1.3
  4. Addedv0.1.1

TDQS

A4.9/5.0
Behavior5/5

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

Annotations already declare read-only, idempotent, non-destructive, but the description adds the exact-URI resolution failure mode and the truncation contract (cut at a code-point boundary, truncated flag, total_chars) that annotations do not convey.

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?

Purpose is front-loaded in the first clause, followed by usage routing, behavior, and truncation semantics in that order. Each sentence adds distinct information with no filler.

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?

For a two-parameter read tool with annotations and an output schema, the description covers routing, failure modes, determinism, and pagination/truncation semantics. Nothing an agent needs before calling is missing.

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

Parameters4/5

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

Schema coverage is 100%, so parameters are already documented. The description nonetheless adds semantic value by explaining what truncation means in terms of returned body versus total_chars, though it restates max_chars behavior rather than extending it.

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?

States a specific verb and resource ('Fetch the full text of one agentic-os methodology document') and pins the identifier to an exact URI. It also contrasts itself with search_methodology, so an agent can distinguish the pair without consulting schemas.

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?

Explicitly says to use it for a document already located, normally via search_methodology, and states the negative case: it resolves exact URIs only, cannot search, and returns an error on a guessed URI. Both when-to-use and when-not-to-use are covered.

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