Skip to main content
Glama

batch

Destructive

Execute several pre-decided Civilization V orders in one ordered call; halt at the first refusal and return per-row results with skipped rows.

Instructions

Many orders in one call, in order, with the turn left open: actions is a list of {tool, args} rows -- the rows every read hands back (actions, call): order, answer and notebook rows alike -- each run as that call and answered under results. The first refusal stops the rest by default, since the state the later rows were reasoned about is no longer certain (stop_on_refusal=false runs them all); the rows not run come back under skipped. force=true takes over this turn's claim when another client of my seat holds it (otherwise the first row is refused with turn_claim). Not inside: the turn's wait / finish / end, a load, the seat, the exit, a batch. Each row changes the game as its order would and cannot be undone; a row's own action_id replays. Use it for several orders already decided; use order for one, and turn(action='finish', actions=[...]) when the same rows should end the turn afterwards. Returns {ok, done, results: [one reply per row], skipped?, hint?}: ok is false when any row was refused.

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

Input Schema

NameRequiredDescriptionDefault
forceNotake over this turn's claim when another client of my seat holds it (default false: the first row is then refused with turn_claim)
actionsYesthe rows to run in order, [{tool, args}], as every read hands them back
stop_on_refusalNostop at the first refused row (default true); false runs them all

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv2.7.1
    • changedInput schema / properties / force / description
      Previous value: -"take over this turn's claim held by another client of my seat"New value: +"take over this turn's claim when another client of my seat holds it (default false: the first row is then refused with turn_claim)"
  2. Addedv2.1.0

TDQS

A4.8/5.0
Behavior5/5

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

Annotations already declare destructive=true, idempotent=false, readOnly=false, but the description adds substantial context beyond them: first refusal halts later rows by default because the reasoned-about state is no longer certain, stop_on_refusal=false runs everything, unrun rows appear under `skipped`, force=true overrides another client's turn claim (otherwise the first row is refused with turn_claim), each row is irreversible, and a row's own action_id replays. This is a rich disclosure of failure modes, claim semantics, and irreversibility that the annotations alone could not convey.

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?

The purpose is front-loaded in the first clause and every sentence carries operational information: payload format, default failure behavior, claim handling, exclusions, alternatives, and return shape. It is dense and parenthetical-heavy, making it harder to scan than necessary, but there is no filler or repetition.

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?

There is no output schema, and the description compensates by describing the return shape ({ok, done, results, skipped?, hint?}) and the condition for ok=false. It also covers prerequisites (turn claim and force), failure semantics, exclusions, and alternatives, which is everything an agent needs to invoke it correctly.

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% and the schema already describes all three parameters, so the baseline is 3. The description adds some meaning beyond the schema: it states rows run 'in order,' explains the rationale for the default stop-on-refusal behavior, notes that each row is answered under `results`, and ties `force` to the turn_claim refusal outcome. It largely mirrors the schema wording for the parameters themselves, which keeps it from a 5.

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?

The description opens with a specific verb and resource ('Many orders in one call, in order, with the turn left open') and immediately defines the payload shape ({tool, args} rows). It distinguishes itself from siblings explicitly by naming `order` for a single order and `turn(action='finish', ...)` when the rows should also end the turn, and by listing what is not allowed inside a batch.

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

Usage Guidelines5/5

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

It gives explicit when-to-use guidance ('Use it for several orders already decided; use order for one, and turn(action='finish', actions=[...]) when the same rows should end the turn afterwards') and explicit exclusions ('Not inside: the turn's wait / finish / end, a load, the seat, the exit, a batch'). The alternatives and the boundary conditions are both stated, leaving little 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