Skip to main content
Glama

meshy_generate

Generate a 3D model from a text prompt or image via Meshy AI, then save the GLB and PBR maps locally for Blender/import workflows; confirms credit spend before starting.

Instructions

Generate a 3D model with Meshy AI from a text prompt (two-stage: geometry preview → texture refine, auto-chained) or a single image (imageUrl or local imagePath). Downloads the resulting GLB + PBR maps to the local work dir (~/.tufan-blox-bridge/assets//) and reports the paths — pair with blender_process (lint/fix) and import_file (upload+insert), or use generate_asset for the whole pipeline in one call. SPENDS MESHY CREDITS (~30 ≈ $0.60 per textured asset): the first call returns a cost estimate and asks for confirm:true unless TUFAN_MESHY_AUTOCONFIRM=1. Generation takes minutes; if waitSeconds runs out you get a taskId to resume with (no re-spend). Needs TUFAN_MESHY_KEY (paid Meshy plan).

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": "meshy_generate"
  }
}

Input Schema

NameRequiredDescriptionDefault
promptNoText description of the model (mutually exclusive with image*)
taskIdNoResume a previous generation instead of starting a new one
confirmNoConfirm the credit spend for a NEW generation
imageUrlNoPublic image URL for image-to-3D
topologyNoMesh topology (default triangle)
enablePbrNoGenerate PBR maps (default true)
imagePathNoLocal image file (.png/.jpg/.webp) for image-to-3D
waitSecondsNoMax seconds to wait before returning a resume taskId (default 120, max 600)
targetPolycountNoTarget triangle count (Meshy default is 30k — ABOVE Roblox's 20k limit; 18000 recommended)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.8/5.0
Behavior5/5

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

Goes well beyond the annotations (readOnlyHint=false, openWorldHint=true, idempotentHint=false) by disclosing the credit cost (~30 ≈ $0.60), the confirm:true gate and its env-var bypass, the multi-minute runtime, the taskId resume without re-spend, and the TUFAN_MESHY_KEY prerequisite. It also says where artifacts land on disk and that paths are reported back.

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?

Purpose is front-loaded and the parenthetical, followed by the cost warning in caps, is easy to scan. It is dense and long, but nearly every clause carries actionable information; only the file-path rendering is slightly verbose.

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?

Despite having no output schema, the description tells the agent what comes back (GLB + PBR maps and their local paths, or a taskId on timeout). Cost, auth, timing, and downstream tool chaining are all covered, which is everything needed for a credit-spending, minutes-long open-world generation call.

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, but the description adds real meaning the schema lacks: taskId resumes without re-spending credits, and the two-stage geometry→texture chain is auto-driven rather than parameter-controlled. It does not explain topology or targetPolycount trade-offs, which the schema already covers adequately.

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 ("Generate a 3D model with Meshy AI") and enumerates both input modes, text prompt and single image. It explicitly distinguishes itself from the sibling generate_asset, which does the whole pipeline in one call.

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 concrete routing guidance: pair with blender_process for lint/fix and import_file for upload+insert, or use generate_asset for the full pipeline. It also names the resume path via taskId when waitSeconds expires, so the agent knows how to continue rather than re-invoke blindly.

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