Skip to main content
Glama

batch_submit

DestructiveIdempotent

Atomically persist prepared batch members within the current task's authorization and submission limits, preserving member identities through restarts and retries.

Instructions

Persist all prepared batch members atomically within current task authorization and submission count. Restart/retry retains member identities. Concurrency remains the task policy.

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>",
      "op_id": "<op_id>"
    },
    "name": "batch_submit"
  }
}

Input Schema

NameRequiredDescriptionDefault
op_idYes
tokenNo
batch_idYes
revisionYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.2/5.0
Behavior4/5

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

The annotations already mark this as write, non-open-world, idempotent, and destructive; the description adds atomic persistence, retry identity preservation, and concurrency policy. It stops short of explaining what is destroyed, what authorization is required, or how failures are surfaced.

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?

Three short sentences, front-loaded with the action and atomicity, with no repetition. The final sentence about concurrency is terse but not wasteful.

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?

The output schema exists and annotations already cover safety traits, but the description leaves all four parameters undocumented and authorization/destruction details opaque. For a destructive submit operation with 0% schema descriptions, this is not complete enough.

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

Parameters1/5

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

Schema description coverage is 0% across four parameters, and the description never maps batch_id, revision, op_id, or token to any meaning. No syntax, constraints, or requiredness context is added beyond the schema names.

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 verb 'Persist' and resource 'prepared batch members' are specific, and atomic scope is stated. It does not explicitly differentiate itself from siblings such as batch_prepare or batch_control, so the routing value is only implicit.

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 phrase 'prepared batch members' implies this is used after a preparation step, but no explicit prerequisite or when-not-to-use guidance is given. It also never says when to choose batch_submit over batch_control or run_submit.

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