Skip to main content
Glama

Start approved independent scenes

aimixer_batch_submit
DestructiveIdempotent

PAID ACTION: submit 1–10 independent, user-approved scene quotes from aimixer_batch_quote. Validates the exact sum, scene IDs, signatures, pricing revision, funds and durable approval before debiting each scene; may return PARTIAL success. A batch is NOT one atomic transaction: successful scenes persist if others fail. Never regenerate completed scenes, and reuse the same batch_id and scene_ids for recovery.

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>",
      "expected_total_coins": "<expected_total_coins>",
      "approval_handle": "<approval_handle>",
      "scenes": "<scenes>"
    },
    "name": "aimixer_batch_submit"
  }
}

Input Schema

NameRequiredDescriptionDefault
scenesYes
batch_idYes
dispatch_limitNo
approval_handleYes
expected_total_coinsYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "additionalProperties": true,
      +  "type": "object"
      +}
  2. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Goes well beyond annotations by disclosing what actually happens to money and state: per-scene debiting, a pre-debit validation list (sum, IDs, signatures, pricing revision, funds, durable approval), and non-atomic partial success where completed scenes persist. The annotations only flag destructive/idempotent; the description supplies the operational consequences an agent needs.

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?

Four sentences, front-loaded with the 'PAID ACTION' cost warning, then validation, then the atomicity caveat, then recovery. No filler and each sentence carries a distinct, decision-relevant fact.

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

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a destructive, paid, partially-failing batch tool this covers cost, validation preconditions, partial-success semantics and idempotent recovery, and an output schema exists so return values need not be explained. The one meaningful omission is dispatch_limit, which is neither described nor explained in the schema and affects how many scenes run concurrently.

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 description coverage is 0%, so the description must carry the burden and largely does: 'exact sum' maps to expected_total_coins, 'signatures' to quote_confirmation, plus pricing_revision, scene IDs, approval_handle and the batch_id/scene_ids reuse rule. The dispatch_limit parameter gets no mention, leaving its concurrency meaning undocumented in both places.

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?

States a specific verb and resource ('submit 1–10 independent, user-approved scene quotes from aimixer_batch_quote'), gives cardinality bounds, and names the quote tool that must precede it. An agent can tell this apart from a single-scene submit or a status read without opening the schema.

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

Usage Guidelines4/5

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

Explicitly gates usage on prior approval ('user-approved scene quotes from aimixer_batch_quote') and gives a when-not rule ('Never regenerate completed scenes') plus a recovery path ('reuse the same batch_id and scene_ids for recovery'). It does not contrast itself with the sibling single-submit tool aimixer_submit, so the alternative-selection story is incomplete.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources