Skip to main content
Glama

Mandarin 3D

Quote a 3D model

quote_file
Idempotent

Slice a 3D model and return its exact price delivered by USPS Ground Advantage. Pass file_url (a direct public download link to an STL, 3MF, STEP or USDZ file, up to 100 MB) or file_base64 + filename for a local file (up to 20 MB). USDZ scans keep their physical size and print in one color. Returns quote_id, size, grams, print time, price and an order_url for this model. For multiple files, call once per file, then send all quote IDs to price_quote in one items array. Takes 5-60 seconds for a new file.

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

Input Schema

NameRequiredDescriptionDefault
qtyNoHow many copies to price. Default 1.
colorNoMain color for the ship-by estimate. Default BLK.
file_urlNoDirect download URL of the model (not a web page that shows it).
filenameNoFile name with extension, e.g. bracket.stl. Required with file_base64.
materialNo"pla" (default) or "petg". PETG is made to order in black or white: we order the filament after you buy, which adds 3 to 5 business days, and the print price is 20% higher. Other materials (TPU, ABS, ASA and more) on request: ask in the designer chat and we reply with a price.
file_base64NoThe model file, base64-encoded. Use for files on the user's machine.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / color
      Added value: +{
      +  "description": "Main color for the ship-by estimate. Default BLK.",
      +  "enum": [
      +    "BLK",
      +    "WHT",
      +    "GRY",
      +    "RED",
      +    "BLU",
      +    "GRN"
      +  ],
      +  "type": "string"
      +}
  2. Changed1 schema field changed
    • addedInput schema / properties / material
      Added value: +{
      +  "description": "\"pla\" (default) or \"petg\". PETG is made to order in black or white: we order the filament after you buy, which adds 3 to 5 business days, and the print price is 20% higher. Other materials (TPU, ABS, ASA and more) on request: ask in the designer chat and we reply with a price.",
      +  "enum": [
      +    "pla",
      +    "petg"
      +  ],
      +  "type": "string"
      +}
  3. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Annotations only say readOnlyHint=false, openWorldHint=true, idempotentHint=true. The description adds material context beyond that: 100 MB URL limit vs 20 MB base64 limit, a 5-60 second latency expectation for new files, the USDZ single-color/physical-size caveat, and the exact return fields including order_url. None of this is recoverable from the annotations.

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 core action and pricing source, then input modes, caveats, return shape, multi-file workflow and latency in a logical order. Every sentence carries information, though the middle block packing size limits, USDZ behavior and return fields is dense enough to slow scanning slightly.

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?

With no output schema, the description carries the burden of explaining returns and does so (quote_id, size, grams, print time, price, order_url). It also covers input transport limits, expected duration and the sibling hand-off, leaving nothing material an agent needs before calling.

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; the description still adds real meaning by warning that file_url must be a direct download link rather than a web page and by attaching the 100 MB / 20 MB transport-specific limits. It does not add anything for qty, color or material beyond the enum descriptions already present, hence not a 5.

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?

"Slice a 3D model and return its exact price delivered by USPS Ground Advantage" gives a specific verb (slice + quote) and resource (3D model file) with the exact pricing basis named. It is clearly distinguishable from price_quote, which the description itself identifies as the multi-item aggregator.

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?

It states exactly how to supply input (file_url for public links, file_base64 + filename for local files) and gives explicit workflow routing: call once per file, then pass all quote IDs to price_quote in one items array. That names both the alternative and the condition that selects it.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources