RushOrderTees

Start a print order

start_print_order

Opens a print order. Use it when the customer wants a design printed on a garment. Call it before asking your own questions: our first reply asks for the design and the garment in words written for the customer. Pass what they have said about the order in context — a phrase or a paragraph is fine. Returns the order_id to use with every other tool, what is still needed, and the next question to ask.

Input Schema

Name	Required	Description	Default
`context`	No	What the customer has said so far, in their own words. Unstructured prose is fine; we parse it and ask for the rest one question at a time. Leave empty to start blank.

Output Schema

Name	Required	Description
`spec`	Yes	The print as the customer has described it so far, beside garment. Null where they have not said; still_needed lists what is missing.
`notes`	Yes	Relay these to the customer.
`saved`	Yes	Whether the order is saved to a customer account (save_progress).
`status`	Yes
`artwork`	No
`choices`	No	Answers the customer can pick from, one set per field ask_next asks about. Offer them as selectable options where your client can, otherwise as a short list. They are suggestions: colors are families and the customer may name any shade, quantity and width may be any number. Send whatever they answer to describe_order.
`garment`	No	The garment on the order, and what mockup_url shows. Name it when you show the picture; when it is provisional, say so.
`options`	No
`ask_next`	No	Ask the customer this, in your own words, and send the answer to describe_order.
`order_id`	Yes
`next_call`	Yes	What to call next, and why.
`expires_at`	No	When an unsaved order expires; null once it is saved to an account or paid.
`mockup_url`	No	The garment on the order, in the customer's color, with their design on it once we have it. An image address: show it as a picture where your client can, never as text or as a link, and never describe it in place of the summary.
`alternatives`	No	Present from the moment several styles fit until the customer picks, beside whatever ask_next asks: show all of them with their summaries and prices, say the first is what we will use unless they choose, and call choose_style with the id they pick (or send "any" to describe_order to keep the first).
`checkout_url`	No	Show it to the customer as one link labeled "Pay and enter shipping", not as a bare address: they see the artwork and total, confirm their email with a code we send them, then pay and enter their address there.
`mockup_views`	No	Every side of the garment, the printed one first: mockup_url with the design, then the other sides plain. Where your client can show pictures, show them all, so the customer sees which sides stay blank.
`still_needed`	Yes	Fields the customer has not told us yet, and any go-ahead we are waiting on for something the order cannot carry.
`chosen_option`	No
`artwork_upload_url`	No	Present until the design is accepted. Show it to the customer as one link labeled "Upload your design", not as a bare address: they drop their design file on that page and it is checked there. You cannot upload for them.

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 26, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Annotations only declare write/non-destructive; the description adds real behavior beyond that: the first reply itself solicits design and garment in customer-facing wording, and the call returns order_id plus outstanding info. It does not say what happens if an open order already exists, which is the main undisclosed trait.

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?

Four short sentences, front-loaded with the action, then usage, then calling convention, then return value. No sentence repeats the schema or wastes space.

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?

An output schema exists, yet the description still summarizes what comes back (order_id, what is still needed, next question), which is appropriate for an entry-point tool the agent will chain from. The missing piece is the already-have-an-order scenario and how it relates to resume_order.

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 `context` fully. The description still adds practical guidance — 'a phrase or a paragraph is fine' — reinforcing that unstructured prose is acceptable without a token limit concern.

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: 'Opens a print order'. It implies entry-point status via 'Returns the order_id to use with every other tool', which indirectly differentiates it from siblings like describe_order or create_checkout, but it never names or contrasts any sibling explicitly.

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 when-to-use ('when the customer wants a design printed on a garment') and an ordering constraint ('Call it before asking your own questions'). It omits when NOT to use it or what to do if an order already exists — a real gap given resume_order is a sibling.

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

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