AgentMade Print on Demand

Place the order and get the payment link

purchase

Idempotent

Turn a quote into an order. Needs quote_id, the full recipient address (it must match the quoted destination) and rights_attestation=true. contact_email is the payer's own email, never the gift recipient's. Returns order_id and payment.url: the order page where the person pays by card, Apple Pay or Google Pay. Nothing is printed until the payment is confirmed. Idempotent per quote_id.

Input Schema

Name	Required	Description
`orders`	No	Many parcels with one payment: one quote_id and one recipient per parcel. Not live yet: call purchase once per quote_id for now.
`quote_id`	No	quote_id returned by quote, for one parcel. Set quote_id or orders, not both.
`recipient`	No	Shipping address. Country, state and postal code must match the quote destination. Send the full address when you have it. If you cannot collect the street address, send only country_code, postal_code (and state_code for US, CA and AU): the person then enters the address on the order page before paying. Required with quote_id.
`gift_message`	No	Short message for the packing slip of a gift. Not printed yet: the answer says so.
`contact_email`	No	Email of the payer, for the order confirmation and the payment receipt. Not the recipient's email: for a gift, the recipient must not see the price. Optional.
`rights_attestation`	Yes	Must be true: confirms the customer owns or is licensed to print all submitted artwork, and that it is not prohibited content.
`payment_capabilities`	No	Payment methods the calling agent can use. "hosted_checkout" = a link that the person opens to pay by card, Apple Pay or Google Pay. Always supported.

Output Schema

Name	Required	Description
`items`	Yes
`notes`	Yes
`total`	Yes
`status`	Yes
`payment`	Yes
`order_id`	Yes	A bearer key: whoever has it can read and cancel the order. Do not share it publicly.
`quote_id`	Yes
`timeline`	Yes
`next_step`	Yes	What the agent should do next, in plain language.
`order_url`	Yes	The order page. The person sees the status there.
`shipments`	Yes
`destination`	Yes	While address_needed: the quoted destination.
`status_reason`	Yes
`address_needed`	Yes	True when purchase had no street address: the person enters it on the order page before paying.
`delivery_estimate_business_days`	Yes	Null when the order ended (cancelled, refunded, rejected, expired or delivered).

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 11, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Adds real value beyond annotations: 'Nothing is printed until the payment is confirmed' and the payment-link flow (card/Apple Pay/Google Pay) are behavioral facts not in the structured fields. The idempotency statement refines idempotentHint=true by scoping it per quote_id. The openWorldHint and destructiveHint=false are left unelaborated.

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?

Dense and front-loaded: the core action leads, followed by required inputs, the email nuance, the return value, and the payment-confirmation constraint. Every sentence carries information and none is wasted.

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?

Given an output schema exists, the return mention (order_id, payment.url) is bonus rather than required, and the description covers preconditions, payment flow, and printing timing. The multi-order 'orders' array path is left entirely to the schema, which is acceptable but slightly thins the guidance.

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 description coverage is 100%, so the schema already documents every parameter, including the contact_email and address-matching rules the description restates. The description adds little param-level meaning beyond what the schema carries, so the baseline 3 is correct.

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 ('Turn a quote into an order') and positions it relative to the quote sibling that must precede it. An agent can immediately tell this is the quote-to-order conversion step, distinct from quote, get_order, or cancel_order.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

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

Gives clear preconditions (needs quote_id, address must match quoted destination, rights_attestation=true) and clarifies the contact_email vs recipient email distinction. It implies the quote-first workflow but never explicitly names quote as the required predecessor or states when NOT to call it.

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

All AgentMade Print on Demand 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.