Skip to main content
Glama

batch_control

DestructiveIdempotent

Pause future batch members, resume pending members, or stop a batch and cancel its active jobs without affecting controls for other batches.

Instructions

Pause future members, resume pending members, or stop one batch and cancel its active jobs. Other batches retain their controls.

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": {
      "batch_id": "<batch_id>",
      "revision": "<revision>",
      "action": "<action>",
      "op_id": "<op_id>"
    },
    "name": "batch_control"
  }
}

Input Schema

NameRequiredDescriptionDefault
op_idYes
actionYes
batch_idYes
revisionYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.4/5.0
Behavior4/5

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

Annotations already declare destructive=true, idempotent=true and readOnly=false; the description adds genuine context beyond them by specifying blast radius ('Other batches retain their controls') and that stopping cancels the batch's active jobs. It does not disclose how revision conflicts or op_id replay behave, which is the remaining behavioral gap.

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?

Two short sentences, with the available actions front-loaded and the scoping guarantee second. Nothing is padded, though 'future members' and 'pending members' are slightly ambiguous vocabulary that could be tightened into the actual action names.

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 return values need no explanation, and the safety profile is carried by annotations. However, for a destructive, revision-guarded mutation with four undocumented required parameters, the description leaves operational essentials (action vocabulary, revision precondition, op_id role) unexplained.

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 description coverage is 0% for four required parameters, so the description must compensate and largely fails: it hints at action values through prose ('pause', 'resume', 'stop') but never states the expected literal values, nor explains batch_id, revision, or op_id. The concurrency and idempotency-key semantics of revision and op_id are completely unaddressed, which matters for a mutation tool.

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?

The description names concrete operations (pause, resume, stop) on a batch and states the key consequence (cancel active jobs), so the agent knows this is a lifecycle-mutation tool. It does not differentiate itself from the sibling task_control, which sounds like the obvious alternative for analogous operations on tasks.

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?

The three action modes are described, which implies when to use this tool, but there is no explicit when-not guidance and no pointer to task_control or to batch_get/batch_list for inspecting state before mutating. Usage is inferable rather than stated.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.