Skip to main content
Glama
Sign In
tripo-studio-mcp

tripo-studio-mcp

by Neko-Yukari
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

tripo_image

Create or edit 2D images from text prompts, reference images, or templates, and expand a single image into front, left, back, and right views for 3D asset workflows.

Instructions

生成 2D 图片（对应官方 text_to_image / generate_image / image_to_multiview）：文字生图、带参考图改图、套模板，或把一张图扩成前/左/后/右四视图。内部接口 image/gen_image_v2 + image/gen_multiview，结果下载为 PNG，可直接给 tripo_generate_image / tripo_generate_multiview 用。套餐内每月有免费生图次数。

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "tripo_image"
  }
}

Input Schema

NameRequiredDescriptionDefault
modelNo默认 gemini_3.1_flash_image_preview（Nano Banana 2）；gemini_3_pro = Nano Banana Pro，gpt_image_2.5_sunburst = GPT Image 2.5
amountNo生成张数 1–4，默认 1（multiview 时固定 1）
promptNo描述；只做四视图且给了 image_paths 时可不填
t_poseNo要求角色摆 T 姿势（便于后续绑定），默认 false
out_dirNo默认 tripo-out/images/<asset_id>
multiviewNo输出四视图。有 prompt 时先生成一张再扩四视图；只有一张 image_paths 时直接拿它扩
resolutionNo默认 1K
image_pathsNo参考图（可选，可多张），用于改图/风格参考
template_idNo模板 id（如角色拆分、T 姿势），用 list_templates:true 查
aspect_ratioNo默认 1:1
wait_secondsNo默认 300 秒
list_templatesNo只列出可用模板，不生成

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.7.0

TDQS

A4.3/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does reasonably well: it discloses the internal endpoints used, that results are downloaded as PNG into out_dir, and that a monthly free quota exists. It omits failure/retry behavior and whether the call blocks for wait_seconds, which keeps it from a 5.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single dense paragraph that front-loads the core purpose and mode list before the implementation details. It is efficient, though the internal endpoint names (image/gen_image_v2) are noise for an agent and the sentence is long enough to be slightly hard to scan.

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 12-parameter, zero-required, no-output-schema tool, the description covers what matters: output format and location, quota, mode selection, and downstream compatibility. Missing only error/async semantics, which is a modest gap given the schema already documents every parameter.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3; the description earns above that by explaining cross-parameter interaction the schema only hints at — that multiview with a prompt first generates one image then expands it, while a single image_paths entry is expanded directly, and that template_id is discoverable via list_templates. It also gives t_pose a purpose (rigging) rather than just a flag.

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 (生成 2D 图片) and enumerates the four modes it covers: text-to-image, reference-image editing, templates, and multiview expansion. It also maps itself against the official API names and clarifies its relationship to the 3D siblings tripo_generate_image / tripo_generate_multiview, so an agent can place it without opening the 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?

The mode list effectively tells the agent when to pick this tool (text prompt, reference image, template, or four-view expansion) and notes the free monthly quota as an incentive. It does not explicitly state when NOT to use it versus the 3D generation siblings, but the downstream-consumption note ('可直接给 tripo_generate_image 用') implies the division of labor.

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

Deploy Server

Other Tools