Mixer AI

Inspect model settings and media requirements

aimixer_options

Read-onlyIdempotent

Use this when an exact MixerAI model family/version is selected and before any estimate or paid quote. Returns authoritative public controls, effective_values, conditional media slots, input modes, overrides and info_text for THIS account: the allowed values and limits can differ between accounts, so read them again before each quote; route_revision changes when they may have. The descriptor.price is the selected default/display value, NOT necessarily the final price with hypothetical video/audio/image inputs; use aimixer_estimate for price comparisons, and aimixer_quote only for a complete real generation. Use effective_values as real defaults for aspect, quality, duration and resolution. Preserve source aspect for image edits if auto is available and the user has not chosen a ratio. Never request provider, routing, payer or billing internal fields from the user.

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": {
      "family": "<family>"
    },
    "name": "aimixer_options"
  }
}

Input Schema

Name	Required	Description	Default
`lang`	No		ru
`family`	Yes
`values`	No
`canvas_project_id`	No
`execution_model_key`	No	Exact Topaz execution_model_key returned by catalog/options.

Output Schema

Name	Required	Description	Default
`ok`	Yes
`kind`	Yes
`family`	Yes
`descriptor`	Yes
`usage_notes`	No
`route_revision`	No
`effective_values`	Yes
`mode_constraints`	Yes
`pricing_revision`	Yes
`remembered_values`	No
`execution_model_key`	No
`effective_mode_constraints`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedNov 4, 2026
- addedOutput schema / properties / remembered_values
```
Added value: +{
+  "additionalProperties": true,
+  "type": "object"
+}
```
First observedNov 1, 2026

TDQS

A4.4/5.0

Behavior5/5

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

Beyond the readOnly/idempotent/closed-world annotations, it discloses that allowed values and limits are account-specific and can drift (route_revision), that descriptor.price is a display default rather than a final price, and that effective_values are the real runtime defaults. It also sets a behavioral boundary about never asking users for provider/routing/payer/billing internals, which is material context the annotations do not carry.

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?

The definition is front-loaded with the usage trigger before the return contents, and each sentence conveys a distinct rule. It is dense but mostly earns its length, with only slight sprawl in the mixed return-contents list and the trailing policy sentence.

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 read-only inspection tool with an output schema, the description supplies the decision context an agent needs: when to call, what the cheap price figure means, and how to use effective_values and source aspect. The remaining gap is input-side coverage of the undocumented parameters, which is left entirely to the schema.

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 only 20% (only execution_model_key is documented), so the description must carry the parameter burden. It only indirectly implies the `family` parameter via 'model family/version' and never explains `values`, `canvas_project_id`, or `lang`, leaving three of five parameters (including the nested object) 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?

The description names a concrete verb and resource (returns authoritative controls, effective_values, media slots, input modes, overrides and info_text for a model family for THIS account) and explicitly separates itself from aimixer_estimate and aimixer_quote. An agent can identify the tool's role 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 Guidelines5/5

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

It gives an explicit trigger ('when an exact MixerAI model family/version is selected and before any estimate or paid quote'), a re-invocation rule ('read them again before each quote; route_revision changes when they may have'), and named alternatives for price comparison and real generation. This is exactly the when/when-not/alternative structure that earns a top score.

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

All Mixer AI tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.