RushOrderTees

Send the design

submit_artwork

Sends the design to be printed when you already hold a public https link to the original file; never ask the customer for one, they upload through the artwork_upload_url from any reply. We check whether it will print well at the requested size and answer in inches, with what to fix if anything. A design you only saw in the chat is not one you hold: never transcribe, redraw or regenerate it; give the customer the artwork_upload_url instead. Artwork can be replaced later.

Input Schema

Name	Required	Description
`filename`	No	The original file name, if known.
`order_id`	Yes	The order_id returned by start_print_order.
`image_url`	No	A public https link to the image (PNG, JPEG or WebP) that you already hold; it survives a new conversation.
`image_base64`	No	The bytes of a file dropped on our order card, sent by the card itself (PNG, JPEG or WebP, no data: prefix). Not for a file the customer put in the chat; they upload through artwork_upload_url.

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.3/5.0

Behavior4/5

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

Beyond the annotations (readOnlyHint=false, destructiveHint=false) it discloses that the call runs a print-quality check at the requested size and returns findings in inches with remediation advice, and that artwork can be replaced afterward — a useful reversibility signal supporting destructiveHint=false. It does not address failure modes, size limits, or what happens if the URL is unreachable.

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?

The main condition is front-loaded and every sentence is about correct invocation. However, the 'never ask the customer / give them artwork_upload_url instead' point is repeated twice, costing a sentence.

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?

Covers the highest-risk failure (submitting a design the agent only saw in chat) and the validation answer, and an output schema handles return values. It omits the relationship between image_url and image_base64, which matters since order_id is the only required parameter.

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 coverage is 100%, so the schema already defines image_url, image_base64, order_id and filename. The description reinforces the image_url precondition but never explains the image_url vs image_base64 choice or that neither is required by schema, so it adds only marginal meaning over the structured fields.

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 ('sends the design to be printed') plus the precondition (you hold a public https link to the original file). An agent can immediately tell this submits artwork, distinct from sibling tools like choose_option or start_print_order.

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 explicit when-to-use ('when you already hold a public https link'), explicit when-not ('never ask the customer for one', 'a design you only saw in the chat is not one you hold'), and names the alternative path (hand out artwork_upload_url). Nothing is left to inference.

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?