Skip to main content
Glama

read_content

Read-only

Read retained Markdown, article, or diagnostics content locally by content ID with offset paging; expired handles never refetch.

Instructions

Read retained Markdown/article/diagnostics locally without writes; expired handles never refetch. Offsets are Unicode code points; continue with next_offset. eof ends this view, not necessarily the untruncated original.

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": {
      "content_id": "<content_id>"
    },
    "name": "read_content"
  }
}

Input Schema

NameRequiredDescriptionDefault
viewNomarkdown
offsetNo
max_charsNo
content_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv7.6.2

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, and the description is consistent with them while adding substantive behavior: reads happen locally, expired handles are not refetched, offsets are counted in Unicode code points, and eof marks the end of the current view rather than the end of the original document. The one gap is that it doesn't say what actually happens on an expired handle (error vs. empty result).

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?

Three compact clauses, front-loaded with the core purpose before the caveats. The telegraphic style ('expired handles never refetch') is dense but each clause carries distinct information; nothing is redundant.

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?

With no output schema, the description must convey return shape, and it only gestures at it via next_offset and eof, leaving the actual payload (text body, diagnostics structure) unspecified. Combined with 0% schema coverage on four parameters, a few more specifics would be needed for an agent to page and size requests reliably.

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?

Schema coverage is 0%, so the description carries the burden, and it partially does: it explains offset units (Unicode code points) and enumerates the three views that map to the view enum. But max_chars is never mentioned (notably its 20000 ceiling), content_id is undefined, and next_offset is referenced without being a declared parameter, which could confuse an agent reading only the schema.

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 and resource: read retained Markdown/article/diagnostics locally, with the scope qualifier 'without writes.' The three view names match the enum, so an agent can tell this is the viewer for already-retained content rather than a fetcher. It stops short of naming a sibling (e.g. get_cached or fetch_paper) as the alternative, so differentiation is inferential.

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?

'Expired handles never refetch' and 'continue with next_offset' give real conditions for use and continuation, which is more than nothing. However, there is no explicit statement of when to choose this over the sibling read/cache tools, nor any prerequisite (e.g. that a handle must first come from a fetch or resolve call).

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