trident-mcp

by mordor-forge

Overview Schema Source Related Servers Discussions Admin

Remote

get_tasks

Read-only

Fetch up to 100 Tripo tasks by ID in a single request. Unknown IDs are listed under 'missed'.

Instructions

Get up to 100 Tripo tasks at once. Unknown IDs are listed under missed.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`task_ids`	Yes	Up to 100 task IDs

Output Schema

TableJSON Schema

Name	Required	Description	Default
`tasks`	Yes
`missed`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed22 schema fields changedv0.4.0Oct 19, 2026

removedInput schema / properties / taskIds

Removed value: -{
-  "description": "Task IDs to query, maximum 100",
-  "items": {
-    "type": "string"
-  },
-  "type": [
-    "null",
-    "array"
-  ]
-}

addedInput schema / properties / task_ids

Added value: +{
+  "description": "Up to 100 task IDs",
+  "items": {
+    "type": "string"
+  },
+  "type": [
+    "null",
+    "array"
+  ]
+}

changedInput schema / required

Previous value: -[
-  "taskIds"
-]New value: +[
+  "task_ids"
+]

removedOutput schema / properties / tasks / additionalProperties / properties / completedAt
```
Removed value: -{
-  "type": "string"
-}
```
addedOutput schema / properties / tasks / additionalProperties / properties / completed_at
```
Added value: +{
+  "type": "string"
+}
```
removedOutput schema / properties / tasks / additionalProperties / properties / createdAt
```
Removed value: -{
-  "type": "string"
-}
```
addedOutput schema / properties / tasks / additionalProperties / properties / created_at
```
Added value: +{
+  "type": "string"
+}
```
removedOutput schema / properties / tasks / additionalProperties / properties / creditsConsumed
```
Removed value: -{
-  "type": "number"
-}
```
addedOutput schema / properties / tasks / additionalProperties / properties / credits_consumed
```
Added value: +{
+  "type": "number"
+}
```
removedOutput schema / properties / tasks / additionalProperties / properties / error
```
Removed value: -{
-  "type": "string"
-}
```
addedOutput schema / properties / tasks / additionalProperties / properties / error_code
```
Added value: +{
+  "type": "string"
+}
```
addedOutput schema / properties / tasks / additionalProperties / properties / error_message
```
Added value: +{
+  "type": "string"
+}
```
changedOutput schema / properties / tasks / additionalProperties / properties / output / additionalProperties
```
Previous value: -falseNew value: +true
```

removedOutput schema / properties / tasks / additionalProperties / properties / output / properties

Removed value: -{
-  "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"
-  }
-}

changedOutput schema / properties / tasks / additionalProperties / properties / output / type
```
Previous value: -[
-  "null",
-  "object"
-]New value: +"object"
```

addedOutput schema / properties / tasks / additionalProperties / properties / queuing_num

Added value: +{
+  "description": "Position in Tripo's queue, when Tripo reports it",
+  "type": [
+    "null",
+    "integer"
+  ]
+}

removedOutput schema / properties / tasks / additionalProperties / properties / rawOutput
```
Removed value: -{
-  "additionalProperties": true,
-  "type": "object"
-}
```

addedOutput schema / properties / tasks / additionalProperties / properties / running_left_time

Added value: +{
+  "description": "Estimated seconds until the task finishes, when Tripo reports it",
+  "type": [
+    "null",
+    "integer"
+  ]
+}

removedOutput schema / properties / tasks / additionalProperties / properties / taskId
```
Removed value: -{
-  "type": "string"
-}
```
addedOutput schema / properties / tasks / additionalProperties / properties / task_id
```
Added value: +{
+  "type": "string"
+}
```

changedOutput schema / properties / tasks / additionalProperties / required

Previous value: -[
-  "taskId",
-  "status",
-  "progress"
-]New value: +[
+  "task_id",
+  "status",
+  "progress"
+]

changedOutput schema / properties / tasks / additionalProperties / type
```
Previous value: -"object"New value: +[
+  "null",
+  "object"
+]
```

Addedv0.3.0Jul 11, 2026

TDQS

A3.8/5.0

Behavior4/5

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

The annotations already declare readOnlyHint=true and openWorldHint=true, so safety is covered. The description adds genuinely useful behavior beyond that: the batch cap and, more importantly, the partial-failure contract that unresolvable IDs surface under 'missed' rather than erroring the whole call. Ordering guarantees and whether all-or-nothing semantics apply are still unstated.

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, both front-loaded and free of filler. The batch limit leads and the edge-case handling follows, so every clause carries information.

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?

An output schema exists, so return-value documentation is not required, and the description still flags the 'missed' key an agent would otherwise have to discover. For a one-parameter batch getter distributed across a 27-tool surface, this is nearly complete; only ordering and duplicate-ID behavior are absent.

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 coverage is 100% and the single parameter already documents 'Up to 100 task IDs', so the description's 'up to 100' largely repeats structured data. It adds only indirect semantics by tying bad IDs to the 'missed' output, a baseline 3 given the schema does the heavy lifting.

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 ('Get ... Tripo tasks') and quantifies the batch scope ('up to 100 ... at once'), which implicitly separates it from the singular get_task sibling in the list. It stops short of explicitly naming that sibling, so an agent must infer the batch-vs-single distinction.

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?

'At once' implies a batch retrieval use case, so the usage context is implied rather than stated. There is no explicit 'use this instead of get_task when...' routing, no mention of when the parallel call is preferable to looping the single-task tool, and no exclusions.

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