trident-mcp

Overview Schema Source Related Servers Score Discussions Admin

task_status

Check progress and current state of async 3D generation or post-processing tasks. Returns statuses like queued, running, success, or failure.

Instructions

Check the status of an async 3D generation or post-processing task. Returns progress info and the current state, such as queued, running, success, failed, cancelled, or expired.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`taskId`	Yes	Task ID from a previous generation or post-processing call

Output Schema

TableJSON Schema

Name	Required	Description	Default
`type`	No
`error`	No
`output`	No
`status`	Yes
`taskId`	Yes
`progress`	Yes
`createdAt`	No
`rawOutput`	No
`completedAt`	No
`creditsConsumed`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed6 schema fields changedv0.3.0Jul 11, 2026

addedOutput schema / properties / completedAt
```
Added value: +{
+  "type": "string"
+}
```
addedOutput schema / properties / createdAt
```
Added value: +{
+  "type": "string"
+}
```
addedOutput schema / properties / creditsConsumed
```
Added value: +{
+  "type": "number"
+}
```

addedOutput schema / properties / output

Added value: +{
+  "additionalProperties": false,
+  "properties": {
+    "baseModelUrl": {
+      "type": "string"
+    },
+    "extra": {
+      "additionalProperties": true,
+      "type": "object"
+    },
+    "imageUrl": {
+      "type": "string"
+    },
+    "imageUrls": {
+      "items": {
+        "type": "string"
+      },
+      "type": [
+        "null",
+        "array"
+      ]
+    },
+    "modelUrl": {
+      "type": "string"
+    },
+    "modelUrls": {
+      "items": {
+        "type": "string"
+      },
+      "type": [
+        "null",
+        "array"
+      ]
+    },
+    "pbrModelUrl": {
+      "type": "string"
+    },
+    "renderedImageUrl": {
+      "type": "string"
+    }
+  },
+  "type": [
+    "null",
+    "object"
+  ]
+}

addedOutput schema / properties / rawOutput

Added value: +{
+  "additionalProperties": true,
+  "type": "object"
+}

addedOutput schema / properties / type
```
Added value: +{
+  "type": "string"
+}
```

First observedApr 15, 2026

TDQS

A4.3/5.0

Behavior4/5

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

No annotations provided, but description discloses that tool returns progress info and current state. For a simple read-only status check, this is sufficient behavioral context.

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, no waste. Every word serves a purpose.

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?

Output schema exists so return values are covered. Description is complete for a simple status check tool with one parameter.

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 covers 100% of parameters. Description adds context that taskId comes from a previous generation or post-processing call, which is helpful beyond the schema's minimal description.

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?

Description clearly states 'Check the status of an async 3D generation or post-processing task' with specific verb+resource. Distinguishes from sibling tools like get_task and get_tasks by emphasizing async tasks.

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?

Description implies usage after starting a task, but does not explicitly state when to use versus alternatives like get_task or get_tasks. No exclusions or prerequisites mentioned.

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