Skip to main content
Glama

read_change

Read-only

Retrieves a paginated file manifest for one active change, helping you locate relevant documents and evidence before reviewing or deciding.

Instructions

Paginated file manifest for one active change; no document bodies. Use read_document for Markdown and exact comments, read_change_file for other text/evidence. Read all relevant pages before deciding.

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_change"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes
limitNo
cursorNo
workspacePathNoTrusted absolute project path from this chat; pass on every call. null selects personal storage. Omission uses only the environment default.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.5.1

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already cover safety (readOnlyHint=true, openWorldHint=false), and the description adds genuinely new behavior: the response is a manifest without document bodies, results are paginated, and full coverage requires traversing pages before concluding. It does not describe cost or per-page limits, leaving a modest gap.

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?

Three short sentences, front-loaded with the resource and its scope, then routing to alternatives, then the pagination rule. No filler and no repetition of the schema.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a read-only, non-open-world tool with no output schema, the description supplies purpose, exclusions (no bodies), sibling routing, and pagination behavior — enough to call it correctly. The remaining gap is parameter-level detail for limit/cursor, which the schema also leaves thin.

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 description coverage is only 25% — only workspacePath is documented in the schema. The description implies pagination (thus limit/cursor) but never explains cursor semantics, the 100-item ceiling, or what 'id' identifies beyond 'one active change', so the low-coverage parameters remain under-specified.

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 resource and shape: 'Paginated file manifest for one active change; no document bodies.' It explicitly distinguishes itself from read_document (Markdown/comments) and read_change_file (other text/evidence), so an agent can pick it without opening another schema.

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?

Names both alternatives and the exact condition that selects each ('read_document for Markdown and exact comments, read_change_file for other text/evidence'). It also gives a procedural rule for this tool's own pagination: 'Read all relevant pages before deciding.'

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