Skip to main content
Glama
Sign In
umbra

umbra

by lxchx
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Route Block Set

route_block_set

Toggle inherited blocking for a tab: enable or disable tracker blocking, replace blocked resource types, or inspect current filter state.

Instructions

Toggle the engine's inherited blocking. trackers: enable/disable the bundled 3520-domain tracker blocklist (yoyo). resource_types: replace the blocked resource-type set (e.g. ['Image','Media','Font'] for fast scraping). Pass nothing to just inspect current state.

Ex: route_block_set('t0', trackers=False) → {"trackers":false,"resource_types":[]} Ex: route_block_set('t0', resource_types=['Image','Font','Media']) Ex: route_block_set('t0') → {"trackers":true,"resource_types":[],"tracker_blocks":42}

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": {
      "tab_id": "<tab_id>"
    },
    "name": "route_block_set"
  }
}

Input Schema

NameRequiredDescriptionDefault
tab_idYes
trackersNo
resource_typesNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.1/5.0
Behavior4/5

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

With no annotations, the description carries the burden and does disclose key traits: the bundled list is a 3520-domain tracker blocklist, and resource_types *replaces* (not augments) the blocked set, which is a meaningful destructive-semantics warning. It omits persistence scope (per-tab vs global), error behavior for invalid resource-type strings, and what happens when only one parameter is supplied.

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?

Purpose is front-loaded, followed by per-parameter semantics and three compact examples covering toggle, set, and inspect. The sentences are dense with no filler, though the examples partially restate the prose above them.

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?

An output schema exists, so return values needn't be explained, and the description still supplies concrete response shapes for the inspect and toggle cases. Combined with the replacement semantics and the inspect-only mode, an agent has enough to call this correctly on a 3-parameter tool.

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 0%, so the description must compensate and largely does: trackers is defined as enable/disable of a specific list, resource_types is defined as a replacement set with concrete legal-looking values ('Image','Media','Font'). tab_id is never described, only demonstrated as 't0' in examples, and valid resource-type strings are not enumerated.

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?

States a specific verb and resource ('Toggle the engine's inherited blocking') and names both controllable dimensions (trackers, resource_types). It is clear what the tool does, but it doesn't explicitly contrast itself with nearby blocking-related siblings such as block_urls or route_add/route_remove.

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?

'Pass nothing to just inspect current state' gives an explicit usage rule for the no-arg case, and the examples show the two mutation modes. There is no guidance on when to prefer this over block_urls/route_add, so selection between overlapping siblings is left to inference.

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