Skip to main content
Glama

read_stored_result

Retrieve a paginated page of a stored result by result_id using offset and limit, so you can inspect large saved outputs without loading everything at once.

Instructions

Read a page of a stored result by result_id, using offset and limit.

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": {
      "result_id": "<result_id>"
    },
    "name": "read_stored_result"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
offsetNo
result_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.3/5.0
Behavior3/5

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

With no annotations, the description carries the full burden. It discloses that this is a read operation and that paging uses offset and limit, but it omits permissions, behavior for invalid result_id values, page stability, defaults, and any error semantics.

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?

The description is a single, front-loaded sentence with no wasted words. The key operation, resource, and pagination parameters are presented immediately.

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?

This is a relatively simple three-parameter read tool, and the description covers the basic operation. However, with no annotations, no output schema, and no schema descriptions, it leaves important context about permissions, errors, and returned page structure unstated.

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 0%, so the description must explain the three parameters. It names result_id, offset, and limit but adds no meaning beyond their names: it does not say what a result_id represents, what offset counts, or what limit defaults/max are.

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?

The description clearly states a specific verb and resource: 'Read a page of a stored result'. It also indicates pagination by result_id, offset, and limit. It does not explicitly differentiate itself from sibling tools such as list_stored_results, but the phrasing still makes the core operation understandable.

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: an agent should use this when it has a result_id and needs a page of that result. There is no explicit guidance on when to choose this over list_stored_results or other siblings, and no stated exclusions.

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