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

Create a checkout link for custom prints

create_checkout

Creates a Stripe Checkout link for one or more custom prints quoted with quote_custom_print, for the person to open and pay in a browser. Nothing is charged by this tool and no order exists until the person pays. Each print is priced again on the server (send checkout_item as quote_custom_print returned it; prices are never taken from the request). Needs the destination ZIP (or country and postal code), since shipping is priced to it. Returns order_link, a drmaker3d.com page that shows the order and opens a fresh payment page, good for 7 days: give the person that. checkout_url is the Stripe page itself, good for two hours. Catalog products, figures, keychains, lithophanes, cake toppers and cookie cutters are bought on their own pages: give the person that page from search_products or print_price_examples.

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": {
      "prints": "<prints>"
    },
    "name": "create_checkout"
  }
}

Input Schema

Name	Required	Description
`zip`	No	U.S. ZIP code it ships to.
`agent`	No	Optional: the name of your agent or service.
`email`	No	The person's own email, supplied with permission. Required when the instant-price email gate is enabled; never invent an address.
`prints`	Yes	Each print's checkout_item from quote_custom_print.
`country`	No	Two-letter country code, default US.
`postal_code`	No	Postal code outside the U.S.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedNov 3, 2026
- changedInput schema / properties / prints / items / properties / copies / maximum
```
Previous value: -100New value: +250
```

Changed1 schema field changedOct 31, 2026

changedInput schema / properties / email / description

Previous value: -"Optional: the person's own email, filled in on the payment page."New value: +"The person's own email, supplied with permission. Required when the instant-price email gate is enabled; never invent an address."

First observedOct 23, 2026

TDQS

A4.9/5.0

Behavior5/5

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

Beyond the annotations, the description discloses critical behavior: nothing is charged, no order exists until payment, prices are re-priced server-side, and the two returned links have different lifetimes and purposes. These are exactly the side-effect and output nuances an agent needs before invoking a non-read-only checkout-link tool.

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

Conciseness5/5

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

The description is a single dense but well-ordered paragraph: purpose first, then charging behavior, quoting requirements, shipping input, return values, and catalog exclusions. Every sentence carries operational information, with no filler.

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 tool with six parameters, a nested prints array, and no output schema, the description is complete enough: it explains the key return fields and validity windows, clarifies that no charge occurs, and states the shipping dependency. Nested print options are left to the schema, which has full coverage.

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 schema already documents all parameters. The description still adds meaningful constraints beyond the schema: prints must be the checkout_item exactly as quote_custom_print returned it, prices are never taken from the request, and ZIP or country/postal code is needed because shipping is priced to that destination.

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?

The description states a specific verb and resource: creating a Stripe Checkout link for custom prints quoted with quote_custom_print. It immediately distinguishes this from buying catalog products, figures, keychains, and other items on their own pages, so an agent can tell it apart from sibling tools without opening 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?

It explicitly scopes use to custom prints quoted with quote_custom_print and tells the agent to send the person to search_products or print_price_examples for catalog products and other predefined items. The when-not-to-use condition is clear and names alternatives.

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 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?