trident-mcp

Overview Schema Source Related Servers Discussions Admin

edit_multiview

Destructive

Correct specific front, left, back, or right views of a multiview image using per-view prompts, creating a Tripo task and returning a task ID to wait on.

Instructions

Correct individual views of an image_to_multiview task with per-view prompts. Creates a Tripo task (spends credits) and returns its task_id immediately; then call wait_for_task.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`input`	Yes	Task ID of an image_to_multiview or edit_multiview task
`prompts`	Yes	1-4 per-view edits (5 credits each)

Output Schema

TableJSON Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

Changed17 schema fields changedv0.4.0Oct 19, 2026

changedInput schema / properties / input / description

Previous value: -"Multiview task ID, image URL, or file token"New value: +"Task ID of an image_to_multiview or edit_multiview task"

removedInput schema / properties / prompt

Removed value: -{
-  "description": "Convenience edit instruction. If view is omitted, applies to all four views",
-  "type": "string"
-}

changedInput schema / properties / prompts / description

Previous value: -"Per-view edit instructions. Each entry requires prompt and view"New value: +"1-4 per-view edits (5 credits each)"

changedInput schema / properties / prompts / items / properties / prompt / description

Previous value: -"Edit instruction for this view"New value: +"What to change in that view"

changedInput schema / properties / prompts / items / properties / view / description

Previous value: -"Target view: front, left, back, or right"New value: +"Which view to edit"

addedInput schema / properties / prompts / items / properties / view / enum
```
Added value: +[
+  "front",
+  "left",
+  "back",
+  "right"
+]
```

changedInput schema / properties / prompts / items / required

Previous value: -[
-  "prompt",
-  "view"
-]New value: +[
+  "view",
+  "prompt"
+]

removedInput schema / properties / view

Removed value: -{
-  "description": "Target view for prompt: front, left, back, or right",
-  "type": "string"
-}

changedInput schema / required

Previous value: -[
-  "input"
-]New value: +[
+  "input",
+  "prompts"
+]

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.2/5.0

Behavior4/5

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

Annotations already declare destructiveHint=true, readOnlyHint=false and idempotentHint=false, so the mutation/unsafe profile is covered. The description adds genuinely new context beyond them: it spends credits and returns task_id immediately, requiring a follow-up wait_for_task call. It does not detail auth or what specifically gets overwritten, but the async/cost behavior is valuable.

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, zero waste: purpose first, then the operational sequence and cost. Front-loaded and immediately actionable.

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?

For a 2-param tool with full schema coverage, annotations covering safety, and an output schema, the description supplies everything required to call it: what it edits, the credit cost, and the required follow-up call. Only minor gaps remain (error behavior, edit limits on an existing 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 100%, so the schema already documents both parameters, including that input is a task ID and prompts are 1-4 per-view edits costing 5 credits each. The description's 'per-view prompts' restates this without adding syntax or format detail. Baseline 3 is appropriate when the schema carries the wording.

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+resource: correcting individual views of an existing image_to_multiview task using per-view prompts. This cleanly distinguishes it from the sibling image_to_multiview, which creates the multiview in the first place. An agent can tell the two apart without opening either 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?

Gives clear workflow context: it operates on an existing multiview task and must be followed by wait_for_task. It names the input lineage (image_to_multiview/edit_multiview task) and the cost implication. It stops short of explicit when-not guidance or naming alternatives, but the operating context is clear.

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