Skip to main content
Glama

scout_network

List the page's fetch and XHR requests with method, path, status and time to tell failed, pending, or never-sent calls apart when the UI and API disagree.

Instructions

List the data requests (fetch and XHR) the current page made since its document loaded: method, path, status and time, oldest first, each marked with the route it was sent from when a client-side route change moved the page since. Use it when the page and the server seem to disagree — an empty list where the API has data, a stale value after a save — to tell a request that failed, one still pending and one that never ran apart. Read-only: it lists what the browser already saw and sends nothing. Credentials in query strings are redacted. A full page load starts a new list; scout_request's own calls are marked.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoHow many of the newest to list. Default 40.
sessionNoTarget this session directly instead of the active one — pass it explicitly when dispatching to MULTIPLE sessions in one turn (e.g. two scout_click calls with different `session`), which then run CONCURRENTLY rather than queueing. Omit for single-session sequential use.
containsNoOnly requests whose path contains this text, e.g. /api/things

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv3.17.0

TDQS

A4.4/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: read-only, sends nothing, credentials in query strings redacted, list resets on full page load, and scout_request's own calls are marked. It also discloses ordering and the route-change annotation of entries — unusually complete behavioral context.

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?

Front-loaded with what is listed and the ordering, then usage and safety notes. Dense but every sentence carries information; slightly long for a single paragraph, but no 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 and no annotations, yet the description covers return content, ordering, the reset lifecycle, redaction, and integration with scout_request. An agent has everything needed to call and interpret it correctly.

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 all three parameters (limit, session, contains) are already documented in the schema, including the concurrency semantics of `session`. The description adds no parameter-specific detail, so the baseline 3 applies.

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 precise verb and resource ('List the data requests (fetch and XHR) the current page made since its document loaded') and enumerates the returned fields (method, path, status, time, ordering). It is clearly distinguishable from siblings like scout_request and scout_navigate.

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?

Gives concrete trigger conditions ('when the page and the server seem to disagree — an empty list where the API has data, a stale value after a save') and the diagnostic goal. It does not name an explicit alternative tool to use instead or state exclusion cases, so it stops short of a 5.

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