Skip to main content
Glama

Start an approved paid generation

aimixer_submit
DestructiveIdempotent

PAID ACTION: use only after explicit human confirmation of one AIMixer quote for precisely the same model, inputs and coin amount. Deducts coins and queues one durable image/video generation, returning a request_id rather than a finished image. The returned price is the quoted customer price; charged_coins is the actual wallet debit (0 for free admin). Requires signed quote_confirmation, pricing_revision, expected_price and account-bound approval_handle. Approval comes from the MCP App's user-clicked confirmation, the MixerAI website, or the user's literal unambiguous reply to the exact-price/model question, forwarded as user_consent_text. Never invent the reply or treat an assistant acknowledgment as consent. Reuse the SAME idempotency_key on uncertain retry; first inspect status if a prior submission may have succeeded.

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>",
      "quote_confirmation": "<quote_confirmation>",
      "pricing_revision": "<pricing_revision>",
      "expected_price": "<expected_price>",
      "idempotency_key": "<idempotency_key>",
      "approval_handle": "<approval_handle>"
    },
    "name": "aimixer_submit"
  }
}

Input Schema

NameRequiredDescriptionDefault
fileNoOriginal image/video/audio ChatGPT attachment, automatically imported before generation. No extra upload tool or public URL is needed.
langNoThe user's conversation language (ru, en, es, pt); the approval card uses it.
familyYes
valuesNoOnly model-public settings returned by aimixer_options.effective_values and its controls. Do not supply provider route, payer IDs, or billing internals.
audio_urlsNo
image_urlsNo
video_urlsNo
source_urlsNo
expected_priceYes
result_originsNo
approval_handleYes
audio_durationsNo
idempotency_keyYes
video_durationsNo
element_payloadsNo
pricing_revisionYes
canvas_project_idNo
file_media_familyNoType of attachment if MIME/name alone is ambiguous.
image_source_urlsNo
user_consent_textNoThe user's EXACT literal response to the price question 'Списать N монет за <model>?' (localized to the user). Only a clear affirmative statement (for example Согласен / I agree / acepto / concordo) authorizes this one signed quote. Never invent, paraphrase or infer the user's response. The original approval_handle and signed quote are still required.
quote_confirmationYes
execution_model_keyNoExact typed execution model advertised by the selected family. Currently used by Topaz; never put provider ids into values.model.
image_urls_by_bucketNo

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. Changed1 schema field changed
    • addedInput schema / properties / lang
      Added value: +{
      +  "description": "The user's conversation language (ru, en, es, pt); the approval card uses it.",
      +  "maxLength": 16,
      +  "minLength": 2,
      +  "type": "string"
      +}
  3. First observed

TDQS

A4.1/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true, idempotentHint=true and readOnlyHint=false, so the mutation/idempotency profile is known. The description still adds real value beyond them: coins are deducted, the call queues rather than completes, expected_price is the quoted price while charged_coins is the wallet debit (0 for free admin). It does not cover failure/refund behavior or whether a failed submission still debits coins, which matters most for a destructive paid action.

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?

Front-loads 'PAID ACTION' and the precondition before the mechanics, which is the right ordering for a destructive tool. Dense but every clause carries a constraint; the approval-source enumeration is the one stretch that could be tightened.

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 23-param destructive paid call the consent, idempotency and pricing semantics are covered well, and an output schema exists so return values need not be spelled out. The remaining gap is input assembly — how to derive family, values and media arrays — which the description leaves largely to the schema.

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?

Schema coverage is only 26% across 23 params, so the description carries a heavy burden; it explains the safety-critical ones (quote_confirmation, pricing_revision, expected_price, approval_handle, user_consent_text, idempotency_key) and disambiguates expected_price from charged_coins. It says nothing about how to populate family/values, file, the *_urls arrays, element_payloads, result_origins, canvas_project_id or execution_model_key, leaving the bulk of the input surface to sparse schema 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?

States a specific verb and resource ('queues one durable image/video generation') plus the immediately relevant consequence ('Deducts coins') and what it returns ('request_id rather than a finished image'). The 'one' scopes it against the batch sibling, so an agent can tell it apart without opening either 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?

Gives an explicit precondition ('use only after explicit human confirmation of one AIMixer quote for precisely the same model, inputs and coin amount'), enumerates the acceptable approval sources, and states exclusions ('Never invent the reply or treat an assistant acknowledgment as consent'). It also routes the retry case: reuse the same idempotency_key, and inspect status first if a prior submission may have succeeded.

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