Skip to main content
Glama

tripo_generate_text

Generate 3D models from text prompts with texture, PBR, and face-count options, then save the result as a GLB file for 3D workflows.

Instructions

文字生成 3D 模型(Studio 订阅额度,H3.1 基准约 55 积分/次)。对应内部接口 operation/text_to_model,参数名与官方文档 text_to_model 一致。默认阻塞等待完成并下载 GLB。

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": {
      "prompt": "<prompt>"
    },
    "name": "tripo_generate_text"
  }
}

Input Schema

NameRequiredDescriptionDefault
pbrNoPBR 材质,默认 true;为 true 时 texture 被强制为 true
quadNo四边面输出,默认 false;开启后输出为 FBX 且面数不超过 150,000
promptYes提示词,英文效果更好
textureNo是否生成贴图,默认 true
compressNo纹理压缩方式,默认 meshopt;geometry 需要在建模软件里先解压
out_pathNo保存路径,默认 tripo-out/<prompt>.glb
auto_sizeNo按真实世界尺寸(米)缩放,默认 false
export_uvNo生成阶段是否做 UV 展开,默认 true;设 false 更快、模型更小
face_limitNo面数上限,不填自适应。v3.1/v3.0 detailed 最多 2,000,000、standard 1,500,000;v2.5 最多 500,000;quad=true 时不超过 150,000
model_seedNo几何随机种子,固定可复现(v2.0 及以上)
visibilityNo模型可见性,默认 shareable
face_presetNo面数预设:low 3万 / medium 15万 / high 80万,优先于 face_limit;游戏资产和 3D 打印建议 low 或 medium
orientationNo自动旋转对齐原图,默认 default;仅 texture=true 时生效
texture_seedNo贴图随机种子(v2.0 及以上)
wait_secondsNo阻塞等待上限,默认 480 秒;超时会返回 id,稍后用 tripo_download 取模型
model_versionNo模型版本,默认 v3.1-20260211(H3.1)。v3.0 = H3.0 快速,v2.5 = H2.5 经典;Nexus-v1.0 / Nexus-v2.0 = 智能网格 P1.0 / P2.0(对应官方 API 的 P1,输出干净拓扑低模)
generate_partsNo分部件生成,默认 false;与 texture/pbr/quad 不兼容
smart_low_polyNo手搓拓扑低模,默认 false;输入复杂时可能失败
texture_qualityNo贴图质量,默认 detailed;standard 为基准,detailed +20、extreme +30 积分
geometry_qualityNo几何精度,默认 detailed(Ultra)
texture_alignmentNo贴图对齐倾向:忠于原图 / 忠于几何,默认 original_image

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.7.0

TDQS

A3.7/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 disclose meaningful traits: it consumes paid Studio credits at a stated rate, blocks until completion, and downloads a GLB artifact. It does not describe failure behavior or what is returned when the wait times out, though the wait_seconds schema field partly covers that.

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?

Three short sentences, front-loaded with the core action and cost, then the API mapping, then the default blocking/download behavior. The internal-interface sentence is the least load-bearing but is still brief.

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 21-parameter generation tool with no output schema and no annotations, the description covers the essentials an agent needs: cost, blocking default, and the produced GLB. It could say more about the returned model id and the handoff to tripo_download, but the wait_seconds field hints at that path.

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 all 21 parameters are already documented in the schema, making 3 the baseline. The description only adds that parameter names mirror the official text_to_model docs, which is a minor navigational aid rather than new semantic content.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb+resource: text prompt to 3D model, with the concrete backend operation (operation/text_to_model) named. It implicitly separates itself from tripo_generate_image and tripo_generate_multiview by input modality, but never names those siblings explicitly.

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

Usage Guidelines3/5

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

The description gives cost and subscription context (Studio quota, ~55 credits) and says it blocks by default, which helps an agent decide whether to call it. It never states when to prefer tripo_generate_image or tripo_generate_multiview instead, nor any prerequisites, so usage is only implied.

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