Skip to main content
Glama

ai_modeling_task_wait

Block until a Tripo task completes and optionally download its generated artifacts, so agents can wait for modeling jobs and retrieve results.

Instructions

Block until a Tripo task finishes; optionally download artifacts.

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": "ai_modeling_task_wait"
  }
}

Input Schema

NameRequiredDescriptionDefault
task_idYes
timeoutNo
downloadNo
output_dirNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.4

TDQS

B3.1/5.0
Behavior3/5

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

Annotations declare readOnlyHint=false, openWorldHint=true, destructiveHint=false, and the description usefully explains why it is not read-only: it can write downloaded artifacts to disk. It does not disclose what happens on timeout expiry, whether the call errors or returns partial state, or that download defaults to true (making the 'optionally' framing slightly at odds with the default).

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?

A single front-loaded clause with zero padding, using a semicolon to separate the core behavior from the optional side effect. Brevity is well executed, though it shades into under-specification rather than tight completeness.

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

Completeness2/5

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

For a blocking operation with a 30-minute default timeout, a filesystem-writing side effect, and four undocumented parameters with no output schema, the description says far too little. An agent cannot tell what the call returns, how failure or timeout manifests, or what output_dir actually receives.

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 0%, so all four parameters (task_id, timeout with default 1800 and max 7200, download default true, output_dir) carry no documented meaning anywhere. The description alludes to optional artifact download but never explains timeout units/limits or where output_dir artifacts land, leaving the schema to do work it visibly does not do.

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?

States a specific verb and resource: 'Block until a Tripo task finishes,' which is meaningfully different from a poll-style getter. It does not name or contrast with the sibling ai_modeling_task_get, so an agent must infer the blocking-vs-polling distinction itself.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

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

'Block until a Tripo task finishes' implies when to use it (waiting for completion) but gives no explicit conditions, no exclusions, and no pointer to ai_modeling_task_get for non-blocking polling. Usage is implied rather than stated.

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

Deploy Server

Other Tools