Skip to main content
Glama

operation_read

Read-onlyIdempotent

Reads lossless pages of a work record or snapshot manifest with offset/limit bounds, returning items and deeper-path links; follow next_offset while more is true.

Instructions

Read lossless pages of a work record. path=['result','files'] reads a snapshot manifest; child paths preserve literal filenames. Objects/arrays return items; long values link to deeper paths. offset is nonnegative; limit/text_limit are positive requested upper bounds, capped at 50 items/4096 characters per page. Text uses character offsets. Follow next_offset while more is true.

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": {
      "operation_id": "<operation_id>"
    },
    "name": "operation_read"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathNo
limitNo
offsetNo
text_limitNo
operation_idYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, non-open-world, so the safety profile is covered. The description adds genuinely useful behavior: page caps of 50 items/4096 characters, offset/limit sign constraints, character-based text offsets, and the next_offset continuation loop.

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?

Five dense sentences, front-loaded with purpose then path semantics then pagination rules; every sentence conveys distinct operational information with no filler.

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?

An output schema exists so return-value explanation isn't required, yet the description still usefully states that objects/arrays return items and long values link to deeper paths. The only real omission is a description of the required operation_id parameter.

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 0%, so the description carries the burden and mostly succeeds: path (with example and literal-filename semantics), offset (nonnegative), limit and text_limit (positive, capped values) are all explained. The required operation_id is never described, leaving one gap.

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+resource: 'Read lossless pages of a work record,' with added scope on what path=['result','files'] yields. It is clear about what is returned (manifest vs. items), though it never differentiates itself from siblings like operation_get or response_read.

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?

Usage is implied by the description (paginate with next_offset while more is true), but there is no explicit when-to-use or when-not-to-use guidance relative to operation_get, response_read, or file_read. An agent must infer the selection rule from the resource named ('work record').

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