Skip to main content
Glama

Modellix Media Generation

modellix_wait_task

Read-onlyIdempotent

Wait up to timeout seconds (default 30, maximum 45) for an existing task. A normal timeout returns the current snapshot and task_id; continue waiting on that ID instead of resubmitting.

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_wait_task"
  }
}

Input Schema

NameRequiredDescriptionDefault
task_idYesPreviously returned task ID.
timeoutNo

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/non-destructive, so the safety profile is covered. The description adds genuinely non-obvious behavior: a timeout is not a failure — it returns the current snapshot and task_id, and the caller should re-wait rather than resubmit. It stops short of describing terminal states (completed/failed) or what the snapshot contains, though the output schema likely carries that.

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 sentences, front-loaded with the wait semantics and ending with the actionable timeout-recovery rule. No filler, no redundancy beyond the harmless restatement of the timeout bounds.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists, so return values need not be described; the description instead covers the two things the schema cannot: units/defaults for the wait window and the correct recovery behavior on timeout. For a two-parameter read-only wait tool this is sufficient to invoke it correctly.

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

Parameters4/5

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

Schema coverage is 50%: task_id is documented but timeout has only numeric bounds and no stated unit. The description supplies the unit ('seconds') and restates default 30 / maximum 45, and clarifies that task_id must be a previously returned ID whose reuse is the intended continuation pattern — meaning beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a specific verb and resource ('wait ... for an existing task') and immediately constrains the operation to an already-submitted task, which separates it from modellix_submit_task. It does not explicitly contrast itself with modellix_get_task (the non-waiting read), so the sibling differentiation is partial rather than complete.

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?

It gives a clear usage condition ('for an existing task') and an explicit corrective instruction: after a timeout, 'continue waiting on that ID instead of resubmitting.' What is missing is guidance on when to call get_task instead of waiting again, which is the most likely agent confusion given the sibling set.

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.