Skip to main content
Glama

network_rules

Idempotent

Intercept browser network traffic to block requests, redirect URLs, modify request headers, or stub responses with synthetic bodies. Rules persist across reloads until explicitly cleared.

Instructions

Network interception, browser-wide, survives reloads until cleared: block requests, redirect URLs, set/remove request headers, or stub responses with a synthetic body (served by a local helper; from HTTPS pages the stub host must be trustworthy).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
bodyNoResponse body (action=stub)
actionYeslist and clear inspect and drop the rules already installed
headerNoHeader name for action=modify_header, e.g. "User-Agent"
statusNoaction=stub
url_filterNodeclarativeNetRequest urlFilter, e.g. "||example.com/api/*"
content_typeNoaction=stubapplication/json
header_valueNoOmit to remove header
redirect_urlNoDestination for action=redirect
header_targetNoresponse = strip content-security-policy / x-frame-options, inject CORSrequest
resource_typesNoLimit the rule to these request types; omitted = all of them
Behavior4/5

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

Annotations show idempotent, not read-only, not destructive. The description adds useful behavioral details: rules survive reloads, stub responses use a local helper, and HTTPS pages require a trustworthy stub host. However, the 'list' and 'clear' actions are omitted from the description, creating a minor gap.

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, front-loaded sentence that efficiently conveys scope, persistence, and capabilities. Every word contributes value with no redundancy.

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?

Covers core interception capabilities but omits actions 'list' and 'clear', the url_filter parameter, and resource_types. The lack of an output schema is not compensated by description. Adequate but not fully comprehensive for a complex tool with 10 parameters.

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 100%, so the baseline is 3. The description summarizes action types but does not add new meaning or detail beyond the schema (e.g., url_filter, resource_types).

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 the tool intercepts network requests browser-wide, survives reloads, and lists specific actions: block, redirect, set/remove headers, stub responses. This distinguishes it from sibling tools like http_request (single request) and monitor_network (monitoring only).

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 implies usage for persistent network rule manipulation but does not explicitly contrast with alternatives like monitor_network or http_request. No 'use this for' or 'if you need' guidance is provided.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/frsorrentino/chrome-bridge'

If you have feedback or need assistance with the MCP directory API, please join our Discord server