Skip to main content
Glama

Price independent scene batch

aimixer_batch_quote

Use when the user wants 1–10 INDEPENDENT MixerAI scenes/jobs whose input media already exists. Returns signed quotes for every scene plus a single server-calculated total, approval_handle and approval_url; no provider job or wallet debit starts here. Never batch a video whose reference is the future output of a scene in the same batch. Human approval of the exact total is required before aimixer_batch_submit, via supported inline MCP App confirmation or the AIMixer website.

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

Input Schema

NameRequiredDescriptionDefault
scenesYes

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.4/5.0
Behavior5/5

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

Beyond the annotations, it discloses that the call returns signed quotes plus a server-calculated total, that no provider job or wallet debit is initiated, and that human approval of the exact total is mandatory before aimixer_batch_submit via inline MCP App confirmation or the website. These are material behavioral facts an agent cannot derive from readOnlyHint=false / destructiveHint=false. The no-debit behavior does not contradict readOnlyHint=false, since a quote/approval resource is still created.

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?

Three sentences, each front-loaded with the operative constraint: eligibility, return/non-effect, then the dependency prohibition and the approval gate. No filler, and the most consequential restrictions (independence, approval) are placed after the trigger rather than buried.

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 nested, single-parameter batch tool with an output schema, the description covers the essentials: batch size, independence, quote-only semantics, and the approval-to-submit gate. It is not fully complete because it says nothing about error/partial-quote behavior or how approval_handle is used across scenes, but nothing critical to correct invocation is absent.

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

Parameters3/5

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

Top-level schema description coverage is 0%, so the description must compensate, and it does partially by capping batch size at 1–10 and stating the independence constraint on scenes. However it does not explain scene_id, intent.family, intent.values, or the dependency rule's effect on how scenes are composed, so the deep nested fields still rely on the schema's own inline text.

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 names a specific action (price/quote) on a specific resource (a 1–10 batch of INDEPENDENT MixerAI scenes) and states the output artifacts (signed quotes, server-calculated total, approval_handle, approval_url). It also distinguishes itself from the sibling aimixer_batch_submit by explicitly saying no provider job or wallet debit starts here.

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?

The opening 'Use when the user wants 1–10 INDEPENDENT MixerAI scenes/jobs whose input media already exists' gives a clear trigger, and the exclusion 'Never batch a video whose reference is the future output of a scene in the same batch' is an explicit when-not. It also names the required next step (aimixer_batch_submit after human approval), though it does not name the tool to use for dependent/chained scenes, leaving that routing to inference.

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