RushOrderTees

Choose a garment

choose_style

Idempotent

Lands the order on one of the alternatives describe_order offered, by id, or on the style already chosen. Use it when the customer picks one of them; a pick in their own words can still go to describe_order. Pass color when they picked a picture from preview_colors or want the style in another shade: the style lands in that shade in one call.

Input Schema

Name	Required	Description
`color`	No	The shade to land the style in, when the customer picked a picture from preview_colors or wants this style in another color. Left out, the order keeps its color.
`order_id`	Yes	The order_id returned by start_print_order.
`style_id`	Yes	The id of the alternative the customer chose, exactly as returned by describe_order, or the style_id of a preview_colors picture.

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

Behavior4/5

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

Annotations only declare the safety profile (not read-only, idempotent, non-destructive); the description adds that the color is applied in the same call ('the style lands in that shade in one call'), which tells the agent no follow-up call is needed. It does not cover what happens on an invalid or stale style_id, or whether a prior choice is replaced.

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?

Three front-loaded sentences: action, routing rule, then the color special case. Mostly earns its place, though the color sentence duplicates what the schema property already says rather than adding new 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?

An output schema exists, so return values need not be explained, and all three parameters are schema-documented. The description supplies the remaining decision-relevant context: when to call it, where free-text picks go instead, and how color composes with the call.

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 all three parameters are already documented. The description restates the color rule almost verbatim from the schema ('picked a picture from preview_colors or wants the style in another shade') and adds no syntax, format, or edge-case detail beyond it, so the baseline of 3 applies.

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?

The description states a concrete action (commit the order onto one of the alternatives returned by describe_order, by id) and a secondary case (the style already chosen). It distinguishes itself from describe_order, but does not differentiate from lookalike siblings such as choose_option or pick_choice, leaving some ambiguity about which selection tool to pick.

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 gives an explicit trigger ('when the customer picks one of them'), an explicit exclusion with a redirect ('a pick in their own words can still go to describe_order'), and a conditional rule for color sourced from preview_colors. Routing is unambiguous for the cases it covers.

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?