Wandy3D

Download a 3D model file

export_model

Idempotent

Download link for a file of one of the user's models: glb, fbx, obj, usdz, stl or glb_draco. Free with a Wandy3D plan, an unlocked model or a model made with an API key; otherwise the answer names a one-time price in credits — tell the user, and only after their yes call again with pay_credits: true.

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": {
      "model_id": "<model_id>"
    },
    "name": "export_model"
  }
}

Input Schema

Name	Required	Description	Default
`format`	No	glb (default), fbx (Unity / Unreal / Blender), obj (zip), usdz (Apple AR), glb_draco (smaller glb), stl (the mesh as it is — for a repaired, print-ready file use check_print)	glb
`model_id`	Yes	model_id from list_models or get_task
`pay_credits`	No	true = buy this model's files with the user's credits at the price the previous answer named. Only after the user agreed.

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 12, 2026

TDQS

A3.9/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 two-step paid-export flow: the first call may only quote a one-time credit price, and purchase requires an explicit user confirmation before pay_credits: true. It does not warn that repeating a paid call could charge again despite idempotentHint=true, nor say anything about link lifetime or file size, which is the main residual gap.

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 tightly packed sentence that front-loads what the tool returns, then the entitlement rules, then the payment escalation. The em-dash clause about telling the user is slightly compressed but nothing is wasted.

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?

With no output schema, the description correctly explains that the result is a download link, and that under a paywall the result is instead a named price — the key return-value shapes. Missing details such as link expiry, link format, or whether the quoted price is time-bound are minor but real omissions for a download tool.

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 the schema already documents format enum, model_id provenance, and pay_credits semantics; the description largely restates the pay_credits flow. Baseline 3 is appropriate since the description adds procedural sequencing but no new parameter meaning.

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 and resource ("download link for a file of one of the user's models") and enumerates supported formats, so the agent knows exactly what comes back. It does not explicitly contrast with get_model or other siblings, so it stops short of a 5.

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 clear conditional usage: free with a Wandy3D plan, an unlocked model, or an API-key model; otherwise the call returns a credit price that must be relayed to the user before re-calling with pay_credits: true. It does not name alternative tools (e.g. check_print is only referenced in the schema, not the description), so the alternative selection is left implicit.

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

All Wandy3D tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?