trident-mcp

Overview Schema Source Related Servers Discussions Admin

image_to_multiview

Destructive

Generate front, left, back, and right views from one reference image for 3D modeling; returns a Tripo task ID to monitor and pass to multiview_to_model or edit_multiview.

Instructions

Generate front, left, back and right views from one reference image. Pass the task ID to multiview_to_model or edit_multiview. Creates a Tripo task (spends credits) and returns its task_id immediately; then call wait_for_task.

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": {
      "input": "<input>"
    },
    "name": "image_to_multiview"
  }
}

Input Schema

Name	Required	Description	Default
`input`	Yes	The reference image: local path, URL, file token or image task ID

Output Schema

Name	Required	Description	Default
`model`	No
`task_id`	Yes
`produces`	Yes
`warnings`	No
`operation`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed12 schema fields changedv0.4.0Oct 19, 2026

removedInput schema / properties / imagePath

Removed value: -{
-  "description": "Local image path to upload as input",
-  "type": "string"
-}

removedInput schema / properties / imageUrl

Removed value: -{
-  "description": "Public image URL to use as input",
-  "type": "string"
-}

changedInput schema / properties / input / description

Previous value: -"Image URL or file token. Mutually exclusive with imagePath and imageUrl"New value: +"The reference image: local path, URL, file token or image task ID"

addedInput schema / required
```
Added value: +[
+  "input"
+]
```
addedOutput schema / properties / model
```
Added value: +{
+  "type": "string"
+}
```
addedOutput schema / properties / operation
```
Added value: +{
+  "type": "string"
+}
```
addedOutput schema / properties / produces
```
Added value: +{
+  "type": "string"
+}
```

removedOutput schema / properties / status

Removed value: -{
-  "type": "string"
-}

removedOutput schema / properties / taskId

Removed value: -{
-  "type": "string"
-}

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

addedOutput schema / properties / warnings

Added value: +{
+  "items": {
+    "type": "string"
+  },
+  "type": [
+    "null",
+    "array"
+  ]
+}

changedOutput schema / required

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

Addedv0.3.0Jul 11, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Beyond the annotations (readOnlyHint=false, destructiveHint=true, openWorldHint=true), the description discloses the two behaviors an agent most needs: the call spends credits and it returns asynchronously with a task_id rather than the finished result. It doesn't quantify cost or note failure/queue behavior, and it is consistent with the destructive/state-changing annotations rather than contradicting them.

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?

Three compact sentences, front-loaded with what is produced, then downstream routing, then the async/credit caveat. Every sentence carries distinct, actionable information.

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-value documentation is unnecessary; the description still covers the async pattern, the credit cost, and the next tool to call. Nothing an agent needs to invoke this correctly is missing.

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?

Only one parameter and schema coverage is 100%, so the schema already explains that 'input' accepts a local path, URL, file token or image task ID. The description adds no format or constraint detail beyond that, which is the expected baseline when the schema does the work.

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?

States a specific verb and output (generate front, left, back and right views) from a specific input (one reference image), which an agent can distinguish from image_to_model, image_to_splat, and text_to_image without opening another schema.

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?

Explicitly routes the output task ID to multiview_to_model or edit_multiview and tells the caller to follow up with wait_for_task, so the pipeline position is clear. It does not say when this is the wrong choice versus image_to_model or edit_multiview, so no exclusions are stated.

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