Skip to main content
Glama
Sign In
Mochi

Mochi

by DevZonayed
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

browser_network_requests

Fetch recent network requests for an active browser tab, filtering by URL, method, status range, or failed requests. Optionally capture request and response headers.

Instructions

Recent XHR / fetch / document / asset requests for the active tab. Returns method, URL, status, mime, duration, success/failure. Filter by URL substring, method, status range, or failedOnly. Body capture is opt-in via includeRequestHeaders / includeResponseHeaders.

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

Input Schema

NameRequiredDescriptionDefault
tabIdNo
urlContainsNo
methodNoGET, POST, etc. Case-insensitive.
statusGteNo
statusLtNo
failedOnlyNoOnly requests that errored or returned >=400.
includeRequestHeadersNo
includeResponseHeadersNo
limitNoMax entries returned (capped at 200).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior3/5

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

The description identifies the tool as a read operation returning network request data, with opt-in body capture. However, 'recent' is not quantified (time window unspecified), and there is no disclosure of permissions, rate limits, or whether only the active tab's requests are included (likely yes). No annotations exist to supplement.

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?

Two sentences: the first front-loads the return data, the second adds filter and body capture options. Every sentence is informative and concise, with no wasted words. However, a more structured format (e.g., bullet points) could improve skimmability.

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 9 parameters and no output schema or annotations, the description is adequate but not comprehensive. It does not define 'recent,' specify request ordering, or explain the purpose of tabId. For a moderately complex tool, it leaves some gaps that an agent would need to infer.

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?

The description adds meaning beyond the schema for several parameters: it explains filtering by URL substring, method, status range, or failedOnly, and clarifies that body capture requires optional flags. This is valuable given only 33% schema coverage, though tabId is not mentioned.

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?

The description clearly states it returns recent XHR/fetch/document/asset requests for the active tab, listing attributes like method, URL, status, mime, duration, and success/failure. This verb+resource combination is distinct among sibling browser tools, which are primarily for navigation, clicking, and snapshotting.

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?

The description explains what the tool does but provides no explicit guidance on when to use it versus alternatives (e.g., browser_console_messages for console logs, browser_snapshot for page state). Usage context is implied solely by the tool name and purpose, not explicitly stated.

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