Skip to main content
Glama

Modellix Media Generation

modellix_get_task

Read-onlyIdempotent

Read one task snapshot immediately, without waiting or submitting. Resources may expire; save required outputs promptly.

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": {
      "task_id": "<task_id>"
    },
    "name": "modellix_get_task"
  }
}

Input Schema

NameRequiredDescriptionDefault
task_idYesPreviously returned task ID.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, and non-destructive, so the safety profile is covered. The description adds a genuinely useful behavioral caveat not present in structured fields: resources may expire and outputs must be saved promptly. It does not describe what a snapshot contains or how an unknown task_id is reported, keeping it below the top mark.

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?

Two short sentences with zero filler; the action and its non-blocking nature are front-loaded, and the expiry warning follows as a single compact caveat.

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 single-parameter, read-only tool with an output schema, the description covers purpose, timing semantics, and the expiry caveat. Minor gaps remain around error behavior for an invalid or expired task_id, but nothing essential to correct invocation is missing.

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?

Only one parameter, and the schema already documents it at 100% coverage as 'Previously returned task ID.' The description adds no further meaning about format, source, or validity constraints, so the baseline of 3 applies.

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 ('Read one task snapshot') and immediately narrows scope with 'without waiting or submitting,' which separates it from modellix_wait_task and modellix_submit_task without needing to name them. An agent can distinguish the retrieval semantics from its siblings on the description alone.

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?

'Immediately, without waiting or submitting' gives a clear condition for choosing this tool over a blocking wait or a submit. It stops short of explicitly naming the alternative or stating when-not-to-use (e.g. when the task has not started), so it is strong context rather than full routing guidance.

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.