Skip to main content
Glama

Modellix Media Generation

modellix_submit_task

Submit one paid media generation request after user confirmation of the model and input. Returns task_id immediately. Never retry an unknown submission automatically; query or wait using the known ID.

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": {
      "model_slug": "<model_slug>",
      "input": "<input>"
    },
    "name": "modellix_submit_task"
  }
}

Input Schema

NameRequiredDescriptionDefault
inputYes
model_slugYesExact provider/model slug.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Goes beyond the annotations by disclosing that the request is paid (a cost consequence the hints do not convey), that it is asynchronous and returns task_id immediately, and that an unknown submission must not be retried. It does not cover auth requirements, rate limits, or failure semantics beyond the retry warning, which keeps it off a 5.

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 short sentences, each carrying a distinct fact: what it does, what it returns, and how to handle the result. The precondition is front-loaded and there is no filler.

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?

The async, paid, non-idempotent profile is well covered and an output schema exists for the return value. However, for a submit tool whose core argument is an opaque nested 'input' object, the absence of any guidance on its contents is a real completeness gap.

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 coverage is only 50%, and the uncovered parameter is the free-form 'input' object with additionalProperties=true and no description. The description never explains what belongs in that object, so the largest semantic gap is left entirely unaddressed; model_slug's exact-slug requirement is already handled by the schema.

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 one paid media generation request') plus scope ('one') and a precondition ('after user confirmation'). The final sentence implicitly separates it from retrieval siblings by pointing at query/wait on a known ID.

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 a clear precondition (user must confirm model and input first) and a clear prohibition (never auto-retry an unknown submission), then redirects to querying/waiting with the known ID. It stops short of naming modellix_get_task or modellix_wait_task explicitly, so the alternative is described behaviorally rather than by name.

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.