Skip to main content
Glama
Sign In

DrMaker3D: custom 3D printing, figures, cookie cutters and gifts

by com.drmaker3d
OverviewDiscussionsAdmin

Instant price for a 3D model file

quote_custom_print

The exact DrMaker3D instant-quote price for printing a person's 3D model file, from the same engine and the same measurements as the instant quote page. Pass the file the person attached (as file), or upload it first: POST https://drmaker3d.com/api/upload as multipart/form-data with fields file (STL, OBJ, 3MF, GLB, glTF or PLY, up to 25 MB) and kind=printiq, and pass the "key" it returns as file_key. The file is kept privately by the studio for the quote. Returns the price, size, turnaround and a checkout_item to pass to create_checkout. Painted multicolor files, STEP files, parts too big for one piece and model links (Printables, Thingiverse, MakerWorld) are quoted by hand: it says so, and request_quote sends them to Rich.

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": {
      "material": "<material>",
      "color": "<color>"
    },
    "name": "quote_custom_print"
  }
}

Input Schema

NameRequiredDescriptionDefault
fileNoThe person's model file as ChatGPT passes an attached file (a link on files.oaiusercontent.com or OpenAI’s own file storage). Give this or file_key.
colorYesA color of that material from print_options, e.g. "Black" or "Matte Charcoal".
emailNoThe person's own email, supplied with permission. Required when the instant-price email gate is enabled; never invent an address.
unitsNoDefault mm. "inches" for an STL or OBJ drawn in inches.
copiesNoHow many of the model, default 1.
finishNoOptional color family, e.g. "PLA Matte", when a color name is in two families.
infillNoPercent, default 15. 50 and up for functional parts.
qualityNoDefault standard. Draft only for parts 100 mm or more across.
file_keyNoThe key POST /api/upload returned (starts with "printiq/"). Give this or file.
materialYesA material from print_options, e.g. PLA, PETG, "TPU (flexible)", ABS, ASA, "Nylon (PA)", PC, PA-CF, PETG-CF.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / copies / maximum
      Previous value: -100New value: +250
  2. Changed1 schema field changed
    • changedInput schema / properties / infill / description
      Previous value: -"Percent, default 20. 50 and up for functional parts."New value: +"Percent, default 15. 50 and up for functional parts."
  3. Changed1 schema field changed
    • changedInput schema / properties / email / description
      Previous value: -"Optional: the person's email. Needed only when the site asks for one before showing exact prices."New value: +"The person's own email, supplied with permission. Required when the instant-price email gate is enabled; never invent an address."
  4. Changed1 schema field changed
    • changedInput schema / properties / file / description
      Previous value: -"The person's model file as ChatGPT passes an attached file (a files.oaiusercontent.com link). Give this or file_key."New value: +"The person's model file as ChatGPT passes an attached file (a link on files.oaiusercontent.com or OpenAI’s own file storage). Give this or file_key."
  5. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Annotations only declare the safety profile (not read-only, not destructive, not idempotent, closed-world). The description adds what annotations cannot: the file is stored privately by the studio, the accepted formats and 25 MB cap, and what the response contains (price, size, turnaround, checkout_item) along with where that item goes next.

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 what the tool does and the cheapest call path, then prerequisites, then return value, then exclusions — a sensible order with no filler. The inline endpoint URL and format list make it dense, but every clause carries actionable information.

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?

For a 10-parameter tool with a nested file object and no output schema, the description covers the input gate (file vs file_key), the return payload, the downstream handoff to create_checkout, and the failure modes that require a human quote. Nothing an agent needs to call it correctly is missing.

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 earns a step up by explaining the relationship between `file` and `file_key` and exactly how to obtain a `file_key` via the upload endpoint — context the schema only hints at. It does not add detail on `units`, `infill`, `quality` or `copies`, which remain schema-only.

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 and resource (instant-quote price for a 3D model file) plus a scope qualifier: same engine and measurements as the public quote page. That scope qualifier distinguishes it from print_price_examples and request_quote without needing their schemas.

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?

Gives both entry paths explicitly: pass an attached file as `file`, or call POST /api/upload with kind=printiq and pass the returned key as `file_key`. It also names the exclusion cases — painted multicolor, STEP, oversized parts, model links — and routes them to request_quote.

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

All DrMaker3D: custom 3D printing, figures, cookie cutters and gifts toolsInspect
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