Skip to main content
Glama

read_item

Read-onlyIdempotent

Fetch an item's original page and extract its main text when the summary is insufficient; set a length limit and use truncation details to retrieve more.

Instructions

The full text of an Item: fetches its original page and extracts the main text.

    Use when an Item's summary is not enough. `id` is an Item's `id` from `whats_new`
    or `search`. `text` is the first `max_length` characters (default 10,000), with no
    marker added; `truncated` says whether that left some out and `full_length` gives
    the whole text's length, so call again with a larger `max_length` for the rest.
    If the page cannot be fetched or has no main text, the error gives the Item's
    summary and link instead.
    

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": {
      "id": "<id>"
    },
    "name": "read_item"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes
max_lengthNo

Output Schema

NameRequiredDescriptionDefault
idYes
urlYes
textYes
titleYes
truncatedYes
full_lengthYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already cover readOnly/idempotent/openWorld, and the description adds real behavioral detail beyond them: truncation with no marker, how to page for the rest via a larger max_length, and the fallback behavior on fetch failure (error returns the summary and link). Lacks only rate-limit or fetch-cost context.

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?

Front-loads the purpose, then usage, parameters, and error behavior in a logical order. Dense but nearly every clause adds meaning, though a couple of the return-field explanations border on redundancy given the output schema.

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, it covers purpose, when to use, parameter sourcing, truncation/pagination mechanics, and failure behavior — enough for an agent to invoke and iterate correctly.

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?

Schema coverage is 0%, so the description carries the burden and does so: `id` is defined as an Item id from `whats_new` or `search`, and `max_length` is explained as the character count (default 10,000) controlling the returned `text`, with `truncated`/`full_length` clarifying how to continue.

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 (fetches original page, extracts main text) and resource (an Item's full text), and distinguishes itself from the summary-returning siblings by framing itself as the escalation when 'an Item's summary is not enough.'

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly says when to use it ('when an Item's summary is not enough') and where to get the `id` (from `whats_new` or `search`). It doesn't spell out an explicit when-not-to-use case, but the routing context is clear.

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

Deploy Server

Other Tools