Skip to main content
Glama
hofmeister

web-ui-tester

by hofmeister
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Request detail

browser_request_detail
Read-only

Inspect a captured browser request to view headers, timing breakdown, request or response bodies, and WebSocket frames for diagnosing network issues.

Instructions

Inspects one request from browser_network: headers, timing breakdown, request body, or response body. Small text responses are cached, so they stay readable after navigation. For a WebSocket entry, any part returns its frame stream.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesThe #id from browser_network.
partNoWhich part to return. Defaults to "summary". Use "frames" for WebSocket entries (shown as WS in browser_network) to read the frame stream.
offsetNoStart offset into the body, for paging through a long one.
maxCharsNo
sessionIdYesSession id returned by browser_start.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / part / description
      Previous value: -"Which part to return. Defaults to \"summary\"."New value: +"Which part to return. Defaults to \"summary\". Use \"frames\" for WebSocket entries (shown as WS in browser_network) to read the frame stream."
    • changedInput schema / properties / part / enum
      Previous value: -[
-  "summary",
-  "headers",
-  "requestBody",
-  "responseBody"
-]New value: +[
+  "summary",
+  "headers",
+  "requestBody",
+  "responseBody",
+  "frames"
+]
  2. First observedv0.1.0

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already cover the read-only/open-world safety profile, and the description adds real behavioral detail beyond them: small text responses remain readable after navigation due to caching, and WebSocket entries return a frame stream regardless of the part requested. Rate limits or paging behavior are not described, but the annotations plus these notes make the behavior reasonably transparent.

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?

Three tight sentences with no filler, and the core action is front-loaded. The caching and WebSocket sentences each carry distinct, useful information rather than restating the schema.

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?

No output schema exists, so the description carries the return-value burden; it names what each part yields and calls out the WebSocket special case. It stops short of explaining paging (offset/maxChars) or response size limits, but covers the essentials for correct invocation.

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 80%, so the baseline is 3, but the description adds semantic mapping for the part values (headers, timing, request/response body) and explains the special frames case for WebSocket entries. Minor mismatch: it says 'timing breakdown' while the enum exposes 'summary'.

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 (inspects) and resource (one request from browser_network) and enumerates the fetchable parts: headers, timing, request body, response body. It also distinguishes itself from the sibling browser_network, which produces the #id this tool consumes.

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?

Implies the ordering: use browser_network first to obtain the #id, then call this to inspect a single entry. It also routes WebSocket entries (shown as WS) to the frames part. No explicit when-not-to-use or fallback, but the context is clear.

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