Skip to main content
Glama
IGELHARINE

CDPM

by IGELHARINE
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Block requests

browser_block

Blocks tab network requests by URL pattern so unwanted resources fail; add, remove, or clear rules for the current session to control page behavior.

Instructions

Blocks tab network requests matching URL patterns (they fail). add adds, remove removes, clear removes all rules you set. Patterns: * any chars, ? one char. A bare domain matches every request containing it ("ads.example.com" → "ads.example.com"). A trailing * is added automatically so query strings still match (".png" → ".png*"). The tab skips the cache while rules exist. Rules last only while this Claude session is alive and are shown to other agents in the header. With no args, shows current rules.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
addNoURL patterns to block
tabNoTarget tab: number (1, 2…) or ID ("t7"). Use the stable ID when agents share a slot. Required for action tools when there are multiple tabs.
slotYesBrowser slot 1-30. "3", "slot 3", "browser 3" → 3. If the user gives a port like 14052, subtract 14049.
agentNoYour display name, shown to other agents. Subagents must always set it. Default "claude-68d9".
clearNoRemove all rules set by this session
removeNoPatterns to unblock
summaryNoOne-line note of what you are doing (e.g. "comparing laptop prices"). Shown in browser_status (not the status line). Omit to keep the previous one.
multiSlotNotrue only when one agent must handle several slots together (e.g. comparing). Normally omit (one agent = one slot; use subagents for the rest)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.6/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 delivers: rules skip the tab cache, rules last only for this session, rules are surfaced to other agents in the header, and matched requests fail. These are non-obvious side effects an agent could not infer from the schema.

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?

Dense but front-loaded: behavior and verbs lead, then pattern syntax, then lifetime/visibility caveats. Every sentence carries operational information, though the pattern-syntax block is lengthy enough to feel compact rather than elegant.

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?

For an 8-parameter mutation tool with no annotations and no output schema, the description covers the essentials: what is blocked, how rules are added/removed/cleared, how patterns are interpreted, session-scoped lifetime, cache side effect, and no-arg read behavior. Nothing critical to correct invocation is missing.

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?

Schema coverage is 100%, so the baseline is 3, but the description adds pattern-language semantics the schema never states: * and ? wildcards, bare-domain expansion ('ads.example.com' → '*ads.example.com*'), and automatic trailing-star addition for query strings. That materially changes how an agent should write add/remove values.

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 specific verb and resource ('Blocks tab network requests matching URL patterns') and immediately clarifies the consequence ('they fail'), which distinguishes it from the read-only browser_network / browser_network_detail siblings. The add/remove/clear verbs are enumerated so the agent knows this single tool covers the whole rule lifecycle.

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?

It tells the agent how each mode is selected (add adds, remove removes, clear removes all, no args shows current rules), which is genuine usage guidance for a multi-mode tool. It does not explicitly say when to prefer this over browser_network for inspecting traffic, but the operating context is clear.

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