trident-mcp

Overview Schema Source Related Servers Score Discussions Admin

image_to_3d

Generate a 3D model from a reference image using a local file path or public URL. Poll task_status for progress and download_model to retrieve the result.

Instructions

Generate a 3D model from a reference image. Provide a local file path or public URL. This is an async operation — use task_status to poll progress and download_model to retrieve the result.

Input Schema

TableJSON Schema

Name	Required	Description
`pbr`	No	Enable PBR materials. When true, Tripo will also enable texture output
`quad`	No	Generate quad mesh output when supported
`texture`	No	Enable texturing. Set false to request a base model without textures
`autoSize`	No	Automatically scale the model to real-world dimensions in meters
`compress`	No	Compression mode. Set to geometry to request geometry compression
`exportUV`	No	Control whether UV unwrapping is performed during generation
`imageUrl`	No	Public URL of the reference image. Mutually exclusive with imagePath
`faceLimit`	No	Target polygon face count
`imagePath`	No	Local file path to the reference image. Mutually exclusive with imageUrl
`modelSeed`	No	Optional seed for geometry generation
`orientation`	No	Model orientation: default or align_image
`textureSeed`	No	Optional seed for texture generation
`modelVersion`	No	Model version (e.g. turbo, v3.0, v3.1, p1). Defaults to the latest supported H3 model
`smartLowPoly`	No	Enable Tripo smart low-poly mesh optimization when supported
`generateParts`	No	Generate semantic mesh parts when supported
`textureQuality`	No	Texture quality: standard or detailed
`geometryQuality`	No	Geometry detail mode for H3 models: standard or detailed
`textureAlignment`	No	Texture alignment priority: original_image or geometry
`enableImageAutofix`	No	Let Tripo optimize the reference image before generation

Output Schema

TableJSON Schema

Name	Required	Description	Default
`status`	Yes
`taskId`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed14 schema fields changedv0.3.0Jul 11, 2026

addedInput schema / properties / autoSize

Added value: +{
+  "description": "Automatically scale the model to real-world dimensions in meters",
+  "type": [
+    "null",
+    "boolean"
+  ]
+}

addedInput schema / properties / compress

Added value: +{
+  "description": "Compression mode. Set to geometry to request geometry compression",
+  "type": "string"
+}

addedInput schema / properties / enableImageAutofix

Added value: +{
+  "description": "Let Tripo optimize the reference image before generation",
+  "type": [
+    "null",
+    "boolean"
+  ]
+}

addedInput schema / properties / exportUV

Added value: +{
+  "description": "Control whether UV unwrapping is performed during generation",
+  "type": [
+    "null",
+    "boolean"
+  ]
+}

addedInput schema / properties / generateParts

Added value: +{
+  "description": "Generate semantic mesh parts when supported",
+  "type": [
+    "null",
+    "boolean"
+  ]
+}

addedInput schema / properties / geometryQuality

Added value: +{
+  "description": "Geometry detail mode for H3 models: standard or detailed",
+  "type": "string"
+}

addedInput schema / properties / modelSeed

Added value: +{
+  "description": "Optional seed for geometry generation",
+  "type": [
+    "null",
+    "integer"
+  ]
+}

changedInput schema / properties / modelVersion / description

Previous value: -"Model version. Defaults to latest"New value: +"Model version (e.g. turbo, v3.0, v3.1, p1). Defaults to the latest supported H3 model"

addedInput schema / properties / pbr

Added value: +{
+  "description": "Enable PBR materials. When true, Tripo will also enable texture output",
+  "type": [
+    "null",
+    "boolean"
+  ]
+}

addedInput schema / properties / quad

Added value: +{
+  "description": "Generate quad mesh output when supported",
+  "type": [
+    "null",
+    "boolean"
+  ]
+}

addedInput schema / properties / smartLowPoly

Added value: +{
+  "description": "Enable Tripo smart low-poly mesh optimization when supported",
+  "type": [
+    "null",
+    "boolean"
+  ]
+}

addedInput schema / properties / texture

Added value: +{
+  "description": "Enable texturing. Set false to request a base model without textures",
+  "type": [
+    "null",
+    "boolean"
+  ]
+}

addedInput schema / properties / textureAlignment

Added value: +{
+  "description": "Texture alignment priority: original_image or geometry",
+  "type": "string"
+}

addedInput schema / properties / textureSeed

Added value: +{
+  "description": "Optional seed for texture generation",
+  "type": [
+    "null",
+    "integer"
+  ]
+}

First observedApr 15, 2026

TDQS

A3.9/5.0

Behavior3/5

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

With no annotations, description carries full burden. It discloses async nature and needing to poll/download, but omits details on destructive actions, auth, rate limits, or file handling specifics.

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 concise, front-loaded sentences: purpose, input, async workflow. No redundant information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/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. However, the description is ambiguous about whether local file path refers to an uploaded file or direct system access, leaving a gap for a tool with 19 parameters.

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 baseline is 3. The description only mentions providing a file path or URL, adding minimal extra meaning over the schema.

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?

The description clearly states the tool generates a 3D model from a reference image, distinguishing it from siblings like text_to_3d and image_to_multiview. It also specifies async behavior.

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?

The description tells when to use (for generating 3D from image) and mentions async workflow with task_status and download_model. It lacks explicit 'when not to use' or alternatives among many siblings.

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