Skip to main content
Glama
Sign In
umbra

umbra

by lxchx
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Get Response Body

get_response_body

Fetch a buffered HTTP response body by request ID to inspect JSON/HTML payloads from captured requests, extract unrendered data, or debug 4xx/5xx responses.

Instructions

Fetch a buffered HTTP response body by request_id. _untrusted=true (server-controlled).

When: paired with get_network_requests — you saw a request, now you want its actual JSON/HTML payload (to extract data the page never rendered, or debug a 4xx/5xx response).

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": {
      "tab_id": "<tab_id>",
      "request_id": "<request_id>"
    },
    "name": "get_response_body"
  }
}

Input Schema

NameRequiredDescriptionDefault
tab_idYes
max_charsNo
request_idYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior3/5

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

No annotations, so the description carries the full burden. It does flag that the content is '_untrusted=true (server-controlled)', a genuinely useful safety note, and that only *buffered* bodies are available — implying some bodies won't be. But it says nothing about truncation by max_chars, what happens when the body was never buffered or has been evicted, or handling of binary/non-text payloads.

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?

Two tight sentences, front-loaded with the core action and followed by a labeled 'When:' block. No repetition of the title, no filler.

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?

The output schema covers return values, so the description needn't describe them. However, for a 3-parameter tool with zero schema documentation, it omits max_chars/truncation semantics and the failure mode when no body is buffered for a request_id — gaps that could cause a mis-specified call or a misinterpreted empty result.

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% across 3 parameters, so the description must compensate and largely does not. Only request_id is implied; tab_id scope and especially max_chars (default 8000) are undocumented, leaving the agent unaware that responses are truncated and controllable.

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 verb and resource ('Fetch a buffered HTTP response body by request_id') and explicitly separates itself from the sibling get_network_requests: that one lists requests, this one returns the payload. An agent can pick between them without opening either schema.

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?

The 'When:' clause gives concrete triggering conditions — after seeing a request, wanting the JSON/HTML payload for extraction or 4xx/5xx debugging — and names the companion tool. It stops short of saying when not to call it (e.g. request not captured, body not buffered, streamed responses), but the positive guidance is strong.

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

Deploy Server

Other Tools