Skip to main content
Glama

ie_request

Inspect a captured IE-mode network request by ID to view its method, URL, status, timing, headers, and decoded request/response bodies, with secrets redacted and body length capped.

Instructions

Show one captured request (id from ie_network): method, URL, status, timing, request and response headers and bodies. Bodies are decoded with the charset from Content-Type, then the charset of the document that made the request, then cp1252; a form body is percent-decoded the same way; gzip/deflate responses are decoded from a copy; binary bodies are summarised as . body_limit (default 20000) caps the characters shown per body. Secrets are redacted. An HTTPS entry is only a tunnel (host, timing).

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": {
      "id": "<id>"
    },
    "name": "ie_request"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes
body_limitNocharacters shown per body (default 20000)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.1

TDQS

A4.6/5.0
Behavior5/5

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

With no annotations, the description carries the full burden and does so: it discloses the charset fallback chain, percent-decoding of form bodies, gzip/deflate decoding from a copy, binary body summarisation, secret redaction, and the important limitation that HTTPS entries are tunnels only (host + timing). These are exactly the surprises an agent would otherwise hit.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The purpose and required-input provenance are front-loaded, then decoding behavior follows. The decoding sentence is dense and long, but every clause conveys a distinct behavior rather than filler.

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?

No output schema exists, so the description must describe the return shape, which it does item by item. For a two-parameter read tool it covers inputs, output contents, and the HTTPS limitation completely.

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 50%, with only body_limit documented in the schema. The description supplies the missing meaning for id (must come from ie_network) and restates the body_limit cap in operational terms (characters shown per body, default 20000), so the gap is largely closed.

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 (show one captured request) and enumerates exactly what is returned: method, URL, status, timing, headers, bodies. The parenthetical '(id from ie_network)' distinguishes it from the sibling listing tool without ambiguity.

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 tells the agent where the required id comes from (ie_network), which is the key selection signal between this tool and the network listing. It does not state explicit exclusions, but the guidance is clear enough to route correctly.

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