Skip to main content
Glama
Sign In
umbra

umbra

by lxchx
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Route Add Many

route_add_many

Bulk-install multiple routing rules in a single round-trip, returning the installed rule IDs. Use it to add many rules at once instead of calling route_add repeatedly.

Instructions

Bulk-install rules in one round-trip. Each item is a dict matching route_add kwargs (must contain at least action). Returns list of installed rule ids.

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>",
      "rules": "<rules>"
    },
    "name": "route_add_many"
  }
}

Input Schema

NameRequiredDescriptionDefault
rulesYes
tab_idYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/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 full burden. It does disclose the mutation ('install rules') and the return shape ('list of installed rule ids'), plus the per-item requirement of an `action` key, which is real added value. It omits whether installed routes are enabled by default, whether they replace or stack with existing routes, and what happens on partial failure.

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 sentences, front-loaded with the action and its benefit ('one round-trip'), then the item contract and return value. No filler and every clause carries information.

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?

An output schema exists, so the returned rule ids need not be explained again, yet the description still omits the meaning of `tab_id`, the interaction with sibling route tools (route_set_enabled, route_remove), and failure semantics for a bulk mutation with no annotations. Adequate for a wrapper, but leaves gaps an agent would hit in practice.

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 description coverage is 0%, so the description must compensate. It usefully defines `rules` as a list of route_add kwargs with a mandatory `action` key, but `tab_id` is never mentioned, leaving it unclear which tab the rules bind to. Partial compensation justifies a 3 rather than a 2.

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 ('Bulk-install rules in one round-trip') and anchors itself to the sibling `route_add` by saying each item matches its kwargs, so an agent can tell it is the batch form of route_add. It stops short of naming route_add explicitly as the alternative for single installs, but the purpose is unambiguous.

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?

'Bulk-install ... in one round-trip' implies the efficiency rationale for choosing this over repeated route_add calls, but usage is only inferred. There is no explicit 'use when installing N rules, use route_add for one' guidance and no stated preconditions such as whether routes must be enabled afterward or whether existing routes conflict.

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