Skip to main content
Glama

RushOrderTees

Save the order to my account

save_progress
Idempotent

Saves the customer's order to their account so they can pick it up from any conversation; a saved order never expires. Needs the customer to be signed in: if they are not, your client will ask them to sign in or create an account with us, then call this again. Applies when a response's notes offer saving, or when the customer asks to save, to come back later, or to keep their order.

Input Schema

NameRequiredDescriptionDefault
order_idYesThe order_id returned by start_print_order.

Output Schema

NameRequiredDescriptionDefault
specYesThe print as the customer has described it so far, beside garment. Null where they have not said; still_needed lists what is missing.
notesYesRelay these to the customer.
savedYesWhether the order is saved to a customer account (save_progress).
statusYes
artworkNo
choicesNoAnswers 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.
garmentNoThe garment on the order, and what mockup_url shows. Name it when you show the picture; when it is provisional, say so.
optionsNo
ask_nextNoAsk the customer this, in your own words, and send the answer to describe_order.
order_idYes
next_callYesWhat to call next, and why.
expires_atNoWhen an unsaved order expires; null once it is saved to an account or paid.
mockup_urlNoThe 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.
alternativesNoPresent 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_urlNoShow 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_viewsNoEvery 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_neededYesFields the customer has not told us yet, and any go-ahead we are waiting on for something the order cannot carry.
chosen_optionNo
artwork_upload_urlNoPresent 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.

  1. First observed

TDQS

A4.7/5.0
Behavior5/5

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

Annotations already mark this as non-read-only, idempotent, and non-destructive, but the description adds important behavioral context: saved orders never expire, cross-conversation persistence, and the authentication flow including automatic sign-in prompting and retry. This is richer than the annotations alone.

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?

The description is compact and front-loaded, with three purposeful sentences covering persistence, authentication, and trigger conditions. No sentence is redundant or wasted.

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. The description covers the essential behavioral context: persistence, authentication requirements, and usage triggers, making it complete for an agent to call the tool correctly.

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%, and the single parameter order_id is already clearly documented in the schema as the ID returned by start_print_order. The description does not add further meaning about the parameter, so it meets the baseline for high schema coverage.

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?

The description states a specific action and resource: saving the customer's order to their account. It also clarifies the key benefit that a saved order can be retrieved from any conversation and never expires, which distinguishes it from transient order operations like start_print_order or resume_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?

It explicitly names when to use the tool: when a response's notes offer saving, or when the customer asks to save, come back later, or keep their order. It also covers the sign-in prerequisite and instructs the client to re-call after authentication.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources