Skip to main content
Glama

get_result

Read-onlyIdempotent

Read the next chunk of a large tool result by result_id and offset to avoid repeating the paid query; concatenate chunks in offset order.

Instructions

Read the next text chunk of a large tool result, without repeating the paid query. Use result_id and next_offset from the previous response, with the same API Key. Concatenate chunks in offset order. Parse only encoding=json; markdown and text are documents. The format is inherited from the original call. Cached results expire after 10 minutes; only the four newest large results in this local server process are retained.

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": "get_result"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum UTF-16 code units to return, not a row or byte count.
offsetNoPosition in UTF-16 code units. Use next_offset from the preceding chunk.
result_idYesTemporary result_id returned by a previous large tool response; use the same API Key.

Output Schema

NameRequiredDescriptionDefault
codeNoMachine-readable error code when the operation fails.
chunkNoA substring of the selected document. Concatenate all chunks before parsing JSON or displaying the full document.
detailNoAdditional problem detail returned by the API.
offsetNoStart position in UTF-16 code units.
messageNoError, delivery, or continuation instructions.
encodingNoHow to read the assembled chunks. Parse JSON only for json.
result_idNoTemporary result identifier. Read subsequent chunks with get_result and the same API Key.
expires_atNoUTC expiry of the temporary result.
request_idNoFlashData request identifier for support and tracing.
http_statusNoUpstream HTTP status, when an upstream request was made.
next_offsetNoNext UTF-16 position; null when the result is complete.
total_charactersNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.7/5.0
Behavior5/5

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

Annotations already declare readOnly/idempotent/non-destructive, so the bar is lower, but the description adds genuinely new operational facts: a 10-minute TTL on cached results, a retention cap of the four newest large results per local server process, the requirement to reuse the same API Key, and inherited formatting from the original call. These are exactly the constraints an agent needs to avoid a failed or repeated paid call.

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?

Four short sentences, front-loaded with the core action, then the mechanics, then the parsing caveat, then the expiry rule. No filler or repetition of schema content.

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?

Since an output schema exists, return shape need not be described. The description covers the remaining unknowns an agent would face: how to chain chunks, encoding discrimination, lifetime and retention of cached results, and the API Key continuity requirement.

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 100%, so the baseline is 3; the description goes slightly beyond by tying the offset parameter to the next_offset value from the prior response and reiterating the same-API-Key constraint for result_id. It does not add units or bounds beyond what the schema already documents for limit and offset.

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?

The description opens with a specific verb and resource: 'Read the next text chunk of a large tool result.' The qualifying clause 'without repeating the paid query' makes the purpose unambiguous and clearly separates this continuation tool from the search/sibling tools that produce large results.

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?

It states the trigger conditions concretely: use result_id and next_offset from the previous response, with the same API Key, and concatenate in offset order. It also gives a scoping rule for parsing ('Parse only encoding=json; markdown and text are documents'). It does not name an alternative tool for the case where the cached result has already expired, which leaves a small gap.

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