Skip to main content
Glama

inspect_network

Capture and inspect browser network activity to identify failed requests, HTTP 4xx/5xx responses, resource types, and failure reasons while excluding sensitive auth tokens and cookies.

Instructions

Capture and inspect network activity: failed requests, HTTP 4xx/5xx responses, resource types, and failure reasons (avoids capturing sensitive auth tokens or cookies).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "inspect_network"
  }
}

Input Schema

NameRequiredDescriptionDefault
clearNoClear network history after reading (default: false).
failed_onlyNoOnly return failed or 4xx/5xx requests (default: true).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.5/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full burden. It does add genuine behavioral context by disclosing that sensitive auth tokens and cookies are deliberately excluded from capture, which matters for privacy and for interpreting results. However, it does not say whether history accumulates across calls, whether prior navigation is needed, or that the tool is read-only (with the exception of the `clear` mutation).

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?

A single sentence, front-loaded with the verb and resource, followed by the concrete payload and a short parenthetical caveat. No filler or restated title.

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?

For a two-flag read tool with no output schema and no annotations, the description covers what is captured but not the shape of the return value (a list? aggregated counts?) or the lifetime of the captured history that `clear` resets. Adequate but leaves an agent guessing about result structure and statefulness.

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?

Schema description coverage is 100%, so both parameters are already documented in the schema and the baseline is 3. The description touches on the failed/4xx/5xx filtering that corresponds to `failed_only`, but says nothing about `clear`, so it adds no meaning beyond the schema.

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 pair ('Capture and inspect') and a specific resource ('network activity'), then enumerates the returned data: failed requests, 4xx/5xx responses, resource types, failure reasons. An agent can tell it is about network traffic rather than console output or DOM inspection, though it never names a sibling to differentiate against.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is implied rather than stated: enumerating 'failed requests' and 'failure reasons' signals a debugging context, but there is no explicit when-to-use, when-not-to-use, or pointer to an alternative such as inspect_console for related diagnostics. The agent must infer that this is the tool for network-level failures.

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