RushOrderTees

Pick a choice

pick_choice

Idempotent

Lands one of the choices the last reply offered beside ask_next, by field and option, exactly as shown. Use it when the customer picks one of them; an answer in their own words goes to describe_order instead.

Input Schema

Name	Required	Description
`field`	Yes	The field of the choices set the customer answered, as the last reply named it.
`option`	Yes	The option the customer picked, exactly as the last reply listed it.
`order_id`	Yes	The order_id returned by start_print_order.

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

A3.6/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=false, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds valuable context — the values must match the last reply exactly and the operation is tied to the ask_next choices set — but never says this mutates the order state or what happens on an invalid field/option pair.

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?

Two sentences, front-loaded with the action and immediately followed by the routing condition; nothing is padding. The opening clause ('beside ask_next') is slightly awkward but does convey the dependency on the prior reply.

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?

All three parameters are documented by the schema, an output schema exists, and annotations cover safety, so the description only needs to add routing and matching semantics — which it does. The remaining gap is the unresolved overlap with choose_option and choose_style.

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% and the field enum is fully enumerated, so the schema does the heavy lifting. The description reinforces exact-match semantics ('by field and option, exactly as shown') but adds little syntax or format detail beyond what the parameter descriptions already state.

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 action ('Lands one of the choices the last reply offered') tied to a concrete resource: the choice set produced by ask_next, keyed by field and option. The scope is clear, but it never distinguishes itself from the close siblings choose_option and choose_style, which sound like they do the same thing.

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?

Explicitly says when to use it ('when the customer picks one of them') and routes free-form answers to describe_order instead. What's missing is guidance on when to use this versus choose_option/choose_style, the ambiguity an agent is most likely to hit.

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?