Skip to main content
Glama

Generate 3D Model (Popcraft)

popcraft_generate_3d

Generate a 3D mesh (GLB) with Tripo3D from a reference image (image-to-3D) or a text prompt (text-to-3D). Use when the user wants a 3D model, mesh, game asset, printable object, VTuber/character base, or "turn this picture into 3D". Pass image_url (a GCS url from popcraft_media_import_url, popcraft_media_upload, or a prior popcraft_generate_image result) for image-to-3D — a single clean subject on a plain background, front or 3/4 view, works best; for a character use an A-pose/T-pose front view. Omit image_url and pass prompt for text-to-3D. Defaults: model_version "tripo-v2.5" (best quality/cost), texture true, pbr true, quad false (triangles — set true for a quad mesh that is easier to edit/rig in Blender; Tripo then returns FBX), geometry_quality/texture_quality "standard" ("detailed" costs more). smart_low_poly produces a game-ready low-poly mesh. style applies a Tripo preset (e.g. "person:person2cartoon", "object:clay", "object:steampunk") — list them via popcraft_models_explore with type:"3d". Set get_cost:true to preflight the exact credit cost WITHOUT submitting — always do this the first time so the user can confirm. Generation takes ~1–3 minutes. On success an interactive result card is shown and refreshes itself — do NOT poll in a loop; call popcraft_job_display at most once if no card is visible. The finished result URL is a downloadable GLB (or FBX when quad=true) that also appears on the Popcraft /model-3d workspace, where it can be refined further with popcraft_postprocess_3d (retopology, retexture, stylize, mesh completion, format conversion). The result includes project — mention where it was saved when the user did not pick a project. Never tell the user how long the job will take or quote any estimate of generation time — the result card shows progress.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pbrNoGenerate PBR material maps (default true; requires texture)
quadNoQuad topology instead of triangles (default false). Better for editing/rigging in Blender; output becomes FBX.
styleNoOptional Tripo style preset id, e.g. "person:person2cartoon", "object:clay" — see popcraft_models_explore type:"3d"
promptNoText prompt (required for text-to-3D; optional refinement hint with an image). Max 500 chars.
textureNoGenerate textures (default true). false = white untextured mesh, cheaper.
get_costNotrue = return the exact credit cost WITHOUT submitting
image_urlNoReference image as a GCS https URL (from popcraft_media_import_url / popcraft_media_upload / a prior result) or gs:// URI. Omit for text-to-3D.
face_limitNoTarget face count, 1000–50000. Omit for adaptive.
project_idNoFile the result into this Popcraft project (id from popcraft_projects). Omit to use the user's current/last-used project (or a default).
project_nameNoFile the result into the project with this title, creating it if needed. Ignored when project_id is set.
model_versionNoTripo model version — default "tripo-v2.5"; "tripo-p1" is premium quality, "tripo-turbo" is fastest/cheapest
smart_low_polyNoGame-ready low-poly output (default false)
negative_promptNoWhat to avoid in the model
texture_qualityNoTexture detail — default "standard"
geometry_qualityNoGeometry detail — default "standard"

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Annotations cover only the safety profile (readOnlyHint=false, openWorldHint=true, idempotentHint=false), leaving the description to add the operational detail, which it does: ~1-3 min runtime, self-refreshing result card, no polling, cost preflight without submission, output format GLB vs FBX under quad, and post-generation refinement path. Strong value beyond structured fields.

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?

Dense but front-loaded: the verb+resource and mode split come first, then inputs, then defaults, then runtime/polling behavior. Every sentence carries an instruction, though the paragraph runs long and packs defaults, quality tiers, and operational caveats into one block that could be split for scannability.

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?

With 15 parameters, no required fields, and no output schema, the burden of explaining returns falls on the description, and it delivers: result is a downloadable GLB (FBX when quad=true), appears on the /model-3d workspace, includes a `project` field to report, and is refinable. Nothing essential to correct invocation is missing.

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 description coverage is already 100%, so the 3 baseline applies; the description still adds real meaning by naming sensible defaults (model_version tripo-v2.5, texture/pbr true, quad false, quality standard), explaining cost/quality tradeoffs for 'detailed' and tripo-p1/turbo, and giving concrete style preset ids. It stops short of covering every parameter (e.g. face_limit, negative_prompt, project_name are left to 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?

States a specific verb (generate) and resource (3D mesh/GLB) and explicitly splits the two modes: image-to-3D via image_url and text-to-3D via prompt. It also names the sibling it hands off to (popcraft_postprocess_3d) and the discovery tool (popcraft_models_explore), so an agent can separate it from generate_image, generate_video, and postprocess_3d without opening a schema.

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?

Gives trigger conditions ('user wants a 3D model, mesh, game asset, printable object, VTuber base'), mode selection rules, preflight guidance (get_cost:true 'always do this the first time'), anti-polling instructions with the job_display fallback, and where to list styles. Alternatives and exclusions are named explicitly.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources