Mandarin 3D

List ready-made parts

list_catalog

Read-only

Ready-made parts customers can customize without a file: personalized name ornament, desk name plate, name keychain, place card holder, cable clips, headphone hooks, wall hook, shelf bracket, spacers, drawer bins, SD card and game card holders, phone and tablet stands, battery organizer, plant pot, key holder, D-shaft replacement knob, pegboard hooks. Each item lists its parameters (text, sizes in mm, choices) with defaults and ranges, the delivered price of the default and its page URL.

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

Input Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 3, 2026

TDQS

A3.7/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered; the description adds genuine behavioral context by describing what each returned item contains (parameter names, mm sizes, choices, defaults, ranges, default price, page URL). It does not mention result size, pagination, or ordering, which keeps it from a 5.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Purpose is front-loaded and the second sentence explaining returned fields is efficient, but the bulk of the text is a long comma-separated product enumeration that reads as catalog copy rather than tool documentation. It aids semantic matching to user requests but is heavier than needed for a no-parameter list tool.

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 input parameters and no output schema, the description's job is to convey what comes back, and it does so (parameters, defaults, ranges, default price, URL). Missing only secondary details such as catalog size or whether results are cached/static, which are minor for a fixed read-only catalog.

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?

The tool takes zero parameters, so there is nothing for the description to disambiguate; baseline 4 applies. The sentence about per-item parameters describes output shape rather than input semantics, which is a reasonable use of the space.

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 ('list ready-made parts customers can customize without a file') and then enumerates the actual catalog items, so an agent can tell this is a browse-the-catalog read. It does not explicitly contrast itself with siblings like quote_catalog_item or quote_file, 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 Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is only implied: the phrase 'customizable without a file' hints this is the entry point for non-upload workflows, but there is no explicit when-to-use, when-not-to-use, or pointer to the quoting/checkout siblings that logically follow. An agent must infer the workflow from the sibling names alone.

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

All Mandarin 3D 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?