trident-mcp

Overview Schema Source Related Servers Discussions Admin

image_to_splat

Destructive

Generate a Gaussian splat (.splat) from one image (PNG, JPEG, or WebP, at least 256 px). This creates a Tripo task and returns a task_id to wait on before use.

Instructions

Generate a Gaussian splat (.splat) from one image. About 30 credits and 4 minutes. 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_splat"
  }
}

Input Schema

Name	Required	Description	Default
`input`	Yes	The source image: local path, URL or file token. PNG, JPEG or WebP, at least 256 px
`model_seed`	No	Seed for the splat

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.

Changed13 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 source image: local path, URL or file token. PNG, JPEG or WebP, at least 256 px"

addedInput schema / properties / model_seed

Added value: +{
+  "description": "Seed for the splat",
+  "type": [
+    "null",
+    "integer"
+  ]
+}

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

Behavior4/5

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

Annotations already declare destructiveHint=true, idempotentHint=false, and openWorldHint=true. The description adds valuable beyond-annotation context: approximate credit cost, duration, the fact that credits are spent, and the asynchronous task-based flow requiring wait_for_task.

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 short sentences, front-loaded with the core action and output format. Each sentence carries distinct, useful information: artifact type, cost/time, and async follow-up.

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?

With an output schema present, the description need not document return values. It covers the key operational facts: what is generated, approximate cost and time, and the required follow-up call. It is complete enough for correct invocation, though it does not explicitly compare against sibling image tools.

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 both parameters are fully documented in the schema. The description adds only the implicit constraint of a single image input and no additional detail about model_seed format or effect. Baseline 3 is appropriate.

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 ('Generate'), a specific output format ('Gaussian splat (.splat)'), and a clear input constraint ('from one image'). This distinguishes it from siblings like image_to_model and image_to_multiview, which produce different artifact types.

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 instructs the agent to follow up by calling wait_for_task after the immediate task_id return. It also gives cost and time expectations, which help set usage context. It does not name alternative sibling tools or state when not to use this one.

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