Wandy3D

List my 3D models

list_models

Read-onlyIdempotent

The user's library, newest first: model_id, name, preview and what was saved with each model (print checks with their verdict, crafts, game packs), plus generations in progress. search finds a model by name; has_output finds the one prepared for printing or for a craft. Free.

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

Input Schema

Name	Required	Description
`limit`	No	How many models to return (1–20, default 10)
`search`	No	Part of a model name to look for
`has_output`	No	Only models with a saved output of this kind, most recent first: print (a print check), papercraft, laser, bricks, flexi, game_pack or any

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 12, 2026

TDQS

A3.7/5.0

Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the bar is lower. The description adds real context beyond them: results are ordered newest-first, in-progress generations are included, and the call consumes no credits.

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 and front-loaded: the payload fields come first, then filter behavior, then cost. The telegraphic, clause-heavy style borders on clipped but every phrase carries information.

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 carries the burden of describing return values and does so adequately, covering identity, preview, attached outputs, and pending generations. Cost and ordering are also covered, leaving only sibling routing unaddressed.

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 coverage is 100%, so the baseline is 3. The description restates search as name matching and has_output as 'prepared for printing or for a craft' but adds no syntax, matching behavior, or precedence details for limit/maximum beyond what the schema already documents.

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?

Names a specific verb and resource (the user's model library) and describes what each entry contains: model_id, name, preview, attached outputs, and in-progress generations. It does not explicitly contrast with get_model or browse_gallery, so a sibling boundary must still be inferred.

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?

Usage guidance is embedded in parameter framing ('search finds a model by name', 'has_output finds the one prepared for printing or for a craft'), and 'Free' signals no credit cost. It stops short of stating when to prefer this over get_model for a single lookup or browse_gallery for discovery.

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?