trident-mcp

Overview Schema Source Related Servers Discussions Admin

upload_file

Destructive

Upload a local image or 3D model to Tripo to obtain a reusable file token. Use only when an input requires a token; direct local paths are usually accepted.

Instructions

Upload a local image or model to Tripo and get a reusable file token. Rarely needed: every input field already accepts local paths.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`path`	Yes	Absolute path of a local image (png, jpg, webp; up to 20 MB) or model (glb, gltf, fbx, obj, stl, 3mf, usdz; up to 150 MB)

Output Schema

TableJSON Schema

Name	Required	Description	Default
`path`	Yes
`bytes`	Yes
`file_token`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed10 schema fields changedv0.4.0Oct 19, 2026

removedInput schema / properties / filePath

Removed value: -{
-  "description": "Local file path to upload to Tripo",
-  "type": "string"
-}

addedInput schema / properties / path

Added value: +{
+  "description": "Absolute path of a local image (png, jpg, webp; up to 20 MB) or model (glb, gltf, fbx, obj, stl, 3mf, usdz; up to 150 MB)",
+  "type": "string"
+}

changedInput schema / required

Previous value: -[
-  "filePath"
-]New value: +[
+  "path"
+]

addedOutput schema / properties / bytes
```
Added value: +{
+  "type": "integer"
+}
```
removedOutput schema / properties / expiresIn
```
Removed value: -{
-  "type": "integer"
-}
```
removedOutput schema / properties / fileToken
```
Removed value: -{
-  "type": "string"
-}
```
addedOutput schema / properties / file_token
```
Added value: +{
+  "type": "string"
+}
```
addedOutput schema / properties / path
```
Added value: +{
+  "type": "string"
+}
```
removedOutput schema / properties / presignedUrl
```
Removed value: -{
-  "type": "string"
-}
```

changedOutput schema / required

Previous value: -[
-  "presignedUrl",
-  "fileToken",
-  "expiresIn"
-]New value: +[
+  "file_token",
+  "path",
+  "bytes"
+]

Addedv0.3.0Jul 11, 2026

TDQS

A4.3/5.0

Behavior3/5

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

Annotations already carry the safety profile (readOnlyHint=false, destructiveHint=true, openWorldHint=true, idempotentHint=false), lowering the bar. The description adds the return artifact (a reusable file token) but does not explain why a mere upload is flagged destructive or what remote state it creates, so it adds only modest context.

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 tight sentences, front-loaded with the purpose and immediately followed by the caveat. Nothing is wasted and every sentence earns its place.

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 values need not be explained, and the single fully-documented parameter plus annotation safety profile leave no gap. For a one-parameter utility, purpose, guidance, and output are all covered.

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 'path' parameter is documented there with formats and size limits, so the schema does the heavy lifting. The description only mirrors it by saying 'local image or model' without adding format or path syntax detail, making the baseline 3 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 and resource ('Upload a local image or model to Tripo') plus the concrete artifact it returns ('a reusable file token'). The 'Rarely needed' framing effectively distinguishes it from the many processing siblings that accept paths directly.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Provides explicit when-NOT-to-use guidance: 'every input field already accepts local paths' tells the agent the default is to call the target tool directly rather than upload first. The condition that would justify this tool (needing a reusable token) is implied clearly.

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