Skip to main content
Glama
Sign In
umbra

umbra

by lxchx
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Route Set Enabled

route_set_enabled

Pause or resume a rule without deleting it, preserving its hit and capture data for later analysis.

Instructions

Pause or resume a rule without removing it. Preserves hits/captures.

Ex: route_set_enabled('t0','r2',False) → {"id":"r2","enabled":false,"hits":12}

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>",
      "rule_id": "<rule_id>",
      "enabled": "<enabled>"
    },
    "name": "route_set_enabled"
  }
}

Input Schema

NameRequiredDescriptionDefault
tab_idYes
enabledYes
rule_idYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4/5.0
Behavior3/5

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

No annotations are provided, so the description carries the burden. It usefully discloses that the operation is reversible and preserves hit/capture state, but says nothing about behavior for unknown rule_id or tab_id, permission/loopback requirements, or failure modes for a mutation tool.

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?

Two short lines: the behavioral guarantee first, then a concrete example. Zero waste, front-loaded, and the example earns its place by showing the response shape.

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?

With an output schema present, the description needn't explain return values, and the example still illustrates them. For a 3-required-param toggle, the only remaining gap is parameter meaning, which the example only partially covers.

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 schema documents only types and names. The worked example implicitly maps positional values to tab_id, rule_id, and enabled, which adds some meaning, but the description never explains what a tab_id or rule_id refers to or their acceptable formats.

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 pair (pause/resume) and resource (a rule), and explicitly contrasts with removal ('without removing it'), which distinguishes it from the surrounding route_remove sibling. An agent immediately knows this is a non-destructive toggle.

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?

Implies when to use it — instead of deleting a route you want to temporarily disable — and 'preserves hits/captures' gives the reason to prefer it over route_remove. No explicit exclusions or error conditions are 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