Skip to main content
Glama
Sign In
umbra

umbra

by lxchx
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Batch

batch

Run multiple tools in one serial round-trip to cut MCP framing overhead and deduplicate composed results.

Instructions

Run N tools in one round-trip, serial. Saves MCP framing + composes w/ dedup.

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": {
      "calls": "<calls>"
    },
    "name": "batch"
  }
}

Input Schema

NameRequiredDescriptionDefault
callsYes
stop_on_errorNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.5/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden. It discloses serial execution, but does not explain failure semantics, stop-on-error behavior, deduplication behavior, or whether batched operations require specific permissions.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is short and front-loaded, but the extreme terseness and abbreviations ('w/', 'MCP framing + composes w/ dedup') sacrifice clarity. The brevity does not earn its place because key behavior and parameter semantics are missing.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/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 need less explanation. However, as an unannotated meta-tool with two parameters at 0% schema coverage, the description is too incomplete for correct invocation—especially regarding error handling and the structure of batched calls.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0%, so the schema does not explain the parameters. The description says 'N tools' but adds no detail about the shape of each entry in 'calls' or what 'stop_on_error' does, leaving both parameters underspecified.

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 action: running N tools in one round-trip, serially. The purpose is distinguishable from the browser-automation siblings, but the description does not clarify how the batched tool calls are structured.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no explicit when-to-use guidance or comparison to executing tools individually. 'Composes w/ dedup' hints at a benefit but does not tell an agent when batching is appropriate or when it should avoid batching.

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