Skip to main content
Glama

Check scene batch progress

aimixer_batch_status
Read-onlyIdempotent

Use this when checking a storyboard batch's progress, partial failures or an uncertain paid batch response. Read-only: accepts the original batch_id and scene_id list; request_ids are optional because the original account/client-scoped IDs can be recovered. Do NOT re-quote or resubmit a batch before reconciling its completed scenes.

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>",
      "scenes": "<scenes>"
    },
    "name": "aimixer_batch_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
scenesYes
batch_idYes

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

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world behavior, and the description reinforces read-only status. It adds genuinely non-obvious context beyond the annotations: request_ids are optional because account/client-scoped IDs can be recovered, and the reconciliation-before-resubmit warning discloses real workflow risk.

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 sentences with the usage trigger front-loaded and no filler; the safety warning is placed last where it reads naturally. Slightly dense phrasing ('uncertain paid batch response') costs a little clarity but nothing is wasted.

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 not be described, and the mutating-adjacent workflow guidance is covered. However, for a polling-style status tool it gives no guidance on how often to poll or how to interpret an incomplete batch beyond the partial-failure mention.

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 0%, so the description carries the burden, and it does explain that batch_id and the scene_id list are the original identifiers while request_id is optional and why. It omits the array cap of 10 scenes and the identifier length constraints, leaving some schema-only details unexplained.

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 verb and resource: checking a storyboard batch's progress, including partial failures and uncertain paid responses. It implicitly distinguishes itself from quote/submit/resubmit actions via the closing warning, though it never names a sibling tool outright.

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?

Gives concrete when-to-use triggers (checking progress, partial failures, an uncertain paid batch response) and a when-not style rule: do not re-quote or resubmit before reconciling completed scenes. No sibling is named as an explicit alternative, so it falls short of a 5.

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