Skip to main content
Glama

meshy_task

Poll status, download GLB and PBR maps, remesh an existing Meshy task to a target polycount, or check remaining credits. Use remesh to fit Roblox's 20k-triangle limit without regenerating.

Instructions

Inspect or act on an existing Meshy task by id: status (poll progress), download (re-fetch fresh signed URLs and save the GLB + PBR maps locally), remesh (retopologize an existing task's model to targetPolycount — 5 credits, textures preserved; use to bring a >20k-tri result under Roblox's limit without regenerating), balance (remaining account credits — no taskId needed). Needs TUFAN_MESHY_KEY.

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_task"
  }
}

Input Schema

NameRequiredDescriptionDefault
actionNoDefault: status
taskIdNoThe Meshy task id (not needed for action: balance)
waitSecondsNoPoll budget for status/remesh (default 120, max 600)
targetPolycountNoFor remesh (default 18000 — safe under Roblox's 20k)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.3/5.0
Behavior4/5

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

Goes well beyond the annotations by disclosing the auth requirement (TUFAN_MESHY_KEY), a concrete cost (remesh = 5 credits), a side effect (download writes GLB + PBR maps locally), and a quality guarantee (textures preserved). It still does not say whether remesh consumes credits on failure or whether download overwrites existing local files, so it is not fully transparent for a non-idempotent, open-world tool.

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?

Front-loaded with the verb and uses inline parentheses to bind each action to its effect, so every clause earns its place. The single very long sentence with nested asides is dense to parse but contains no filler.

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?

No output schema exists, yet the description sketches what each mode yields (progress, saved files, retopologized model, credit count) and covers the auth prerequisite and cost model. A few residual gaps—failure behavior and local file overwrite semantics—keep it from being fully complete.

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: it explains why targetPolycount exists (textures preserved, staying under Roblox's 20k-tri limit at 5 credits) and clarifies waitSeconds as a poll budget for status/remesh. taskId's exemption for balance is also restated usefully in prose.

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+resource ("Inspect or act on an existing Meshy task by id") and then enumerates each mode with distinct semantics: status=poll progress, download=re-fetch signed URLs and save GLB+PBR maps, remesh=retopologize to targetPolycount, balance=remaining credits. Because it works on an existing task by id, it is clearly separable from the meshy_generate sibling.

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?

Gives concrete when-to-use guidance per mode, notably for remesh ("use to bring a >20k-tri result under Roblox's limit without regenerating") and balance ("no taskId needed"). It does not explicitly name the alternative tool or state when NOT to use it, so it stops short of full routing guidance.

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