Skip to main content
Glama

app_network

Inspect and filter live app HTTP requests (fetch/XHR) by URL, status, or failure, with timing and optional truncated request/response bodies to debug network activity.

Instructions

HTTP requests made by the app (fetch/XHR) with status, timing and truncated bodies.

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": "app_network"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNodefault 30
sinceNo
bodiesNoinclude request/response bodies (default false)
searchNosubstring of URL
failedOnlyNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full burden. It does disclose two useful behavioral traits beyond the schema: only fetch/XHR traffic is captured, and bodies are truncated, which sets expectations about data fidelity. It does not say whether this reads a live buffer or persisted capture, whether auth/permissions are needed, or how results are ordered or paged.

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?

One tight sentence with no filler, and the most informative detail (fetch/XHR scope) is front-loaded. It is a fragment rather than a full clause, which slightly reduces standalone readability but costs no tokens.

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?

With five parameters, no annotations and no output schema, the description should say more: the shape of returned entries, ordering, and how since interacts with limit are all left implicit. The truncated-body note is helpful but not enough to fully brief an agent on calling this with the documented filters.

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 coverage is 60%, so the schema already documents limit, bodies and search, leaving since and failedOnly undocumented. The description clarifies that bodies are truncated (softening the bodies flag) but adds no meaning for the unbounded integer since or the failedOnly boolean. Baseline 3 fits given the schema does most of the work.

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?

The description names the concrete resource (HTTP requests made by the app), scopes it to fetch/XHR, and lists the payload contents (status, timing, truncated bodies). It is a noun phrase without an explicit verb, but it is specific enough to distinguish this data source from siblings like app_logs or app_snapshot.

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

Usage Guidelines2/5

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

There is no when-to-use guidance, no mention of when to prefer this over app_logs for app-level logging, and no prerequisites such as whether request capture must be enabled first. The agent must infer the use case from the title alone.

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