Skip to main content
Glama

Fetch a result's full payload

fetch_raw
Read-only

Retrieves the complete, unshaped backend payload for a result handle when an earlier response was truncated, so you can access the remaining data.

Instructions

The backend's full, unshaped payload for a handle: instant, but can be very large. Use it when a result was cut and you need the rest. Session URLs and credentials in browser payloads are redacted.

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": {
      "handle": "<handle>"
    },
    "name": "fetch_raw"
  }
}

Input Schema

NameRequiredDescriptionDefault
handleYesThe handle an earlier result carried.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.13.0

TDQS

A4/5.0
Behavior4/5

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

Annotations already cover safety (readOnlyHint, openWorldHint=false), and the description adds real context on top: the call is instant, the payload can be very large, and session URLs and credentials in browser payloads are redacted. The redaction note is important disclosure that annotations do not carry.

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 what the tool returns and its cost characteristics, followed by the usage trigger and the redaction caveat. 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?

For a one-parameter read with no output schema, the description covers cost (instant but potentially very large), the trigger for using it, and security-relevant redaction behavior. It is nearly complete; it does not say whether oversized payloads are truncated or pageable, which would be useful given the size warning.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

There is a single parameter with 100% schema coverage, so the schema already explains the handle. The phrase 'handle an earlier result carried' reinforces the provenance requirement but adds no format or retrieval detail beyond the schema, so this sits at baseline.

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 and resource: returns the full, unshaped payload for a handle. The word 'unshaped' implicitly contrasts this with shaping siblings like extract or answer, though no sibling is named directly.

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?

'Use it when a result was cut and you need the rest' gives a concrete trigger condition tied to truncated results. It does not name an alternative or state when not to use it, but the trigger is specific enough that an agent can decide.

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