Skip to main content
Glama

ai_modeling_task_get

Read-only

Retrieve the status and details of a Tripo task using its task ID, enabling agents to inspect progress, results, and next steps.

Instructions

Get the status/details of a Tripo task by 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": {
      "task_id": "<task_id>"
    },
    "name": "ai_modeling_task_get"
  }
}

Input Schema

NameRequiredDescriptionDefault
task_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.4

TDQS

C2.9/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is covered structurally. The description adds only that task state is returned, with no mention of what a terminal/in-progress/failed status looks like, whether repeated polling is safe, or how long results are retained.

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?

One short sentence with the resource and lookup key front-loaded and zero filler. It is efficient, though the terseness is partly the source of the missing usage and return-value guidance.

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?

There is no output schema, so the description is the only place an agent could learn what 'status/details' contains. For a polling-style status getter this gap matters: the agent cannot tell which fields to expect, whether the call is cheap to repeat, or how to interpret a failed task.

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 description coverage is 0%, so the schema gives no meaning for task_id beyond type string. The description says lookup is 'by id', confirming the parameter is a task identifier, but adds nothing about where the id comes from (likely a creation call's response) or its format.

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 + resource: retrieves status/details of a Tripo task identified by id. An agent can tell this is a read of task state rather than a creation or mutation. It does not distinguish itself from look-alike siblings such as ai_modeling_task_wait or ai_modeling_job_get, so it stops short of a 5.

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

Usage Guidelines2/5

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

No guidance on when to call this versus polling alternatives like ai_modeling_task_wait, nor on how often to call it while a task is running. The only implied usage cue comes from the word 'status' in the description.

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