Skip to main content
Glama

network_route

Abort a tab’s requests to an exact URL or return a custom stub response to test page behavior under network failure or mocked content.

Instructions

Make a tab's requests to url fail (abort) or get a stub response (respond), to test how the page copes.

url must match exactly, query included: no wildcards. respond answers with status, body and content_type.
It applies to that tab and its frames, and only while the tab is on an allowlisted site. Returns a route id
for network_unroute. Routes are kept in memory and end when zenpilot disconnects from Zen, after 2 minutes
without tool calls. Off unless the user set allow_request_mocking = true in zenpilot's config.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "url": "<url>"
    },
    "name": "network_route"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYes
bodyNo
actionNoabort
statusNo
tab_idNo
content_typeNotext/plain

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.7.0

TDQS

A4.3/5.0
Behavior4/5

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

With no annotations, the description carries the disclosure burden well: it covers scope (tab and its frames), allowlist restriction, in-memory lifetime, the 2-minute idle expiry, connection-scoped cleanup, the returned route id, and the off-by-default config gate. It doesn't state precedence with existing routes or whether already-issued requests are affected.

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-loads the core behavior in the first sentence, then layers constraints in short sentences. There is some density in the closing sentence about lifecycle and config, but nothing is filler.

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?

For a 6-parameter mutation tool with no annotations and no output schema, most of what an agent needs is present, including the return value and cleanup path. The main omission is tab_id semantics and behavior against in-flight requests.

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 0%, so the description must supply all parameter meaning. It explains url exact matching and how action, status, body, and content_type interact, but never mentions tab_id, which is the parameter an agent most needs clarified (e.g., null default meaning current tab).

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 concrete verb and resource ("Make a tab's requests to url fail ... or get a stub response") and frames the purpose (testing how the page copes). It is clearly distinguishable from network_unroute, which it references for cleanup.

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

Usage Guidelines5/5

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

Explicitly gives the two modes, the condition that selects respond vs abort, the exact-match requirement, the allowlist precondition, and the config flag that must be on. It also names the sibling needed to remove the route.

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