Skip to main content
Glama

Get an agentic-os document

get_document
Read-onlyIdempotent

Retrieve the full text of an agentic-os methodology document by its exact URI. Use it after locating a document via search_methodology to get its contents.

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.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
uriYesAn 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.
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

TableJSON 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.
Behavior5/5

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

Beyond annotations (readOnlyHint, idempotentHint), the description adds that the tool is read-only, idempotent, and explains truncation behavior with max_chars including code-point boundary handling. No contradictions.

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?

Description is efficient with no wasted words, but could be slightly more structured (e.g., separate sections). Still, it is front-loaded with purpose and key constraints.

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?

Given the tool's simplicity (2 params, output schema exists), the description covers purpose, usage, parameter semantics, and behavioral details fully. References output schema elements like total_chars.

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

Parameters5/5

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

With 100% schema coverage, the description still adds value: provides examples and source for the uri parameter, and clarifies that max_chars counts Unicode code points, not UTF-16 units.

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?

The description clearly states the tool fetches the full text of an agentic-os document by its exact URI. It uses a specific verb ('Fetch') and resource, and distinguishes itself from sibling tool search_methodology by noting that search_methodology provides the URI.

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 tells when to use it ('to read a document you have already located') and when not to ('cannot search'); identifies the sibling tool search_methodology as the alternative for locating documents. Also explains that guessed URIs return errors.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Jarroslav/agentic-os'

If you have feedback or need assistance with the MCP directory API, please join our Discord server