Skip to main content
Glama

RushOrderTees

Describe the order

describe_order

Records more about what the customer wants — an answer to ask_next, a correction, or a whole paragraph — and reports what is still needed. Call it each time the customer gives a new detail. In clients that render our app the customer sees their design on the garment when it changes, and the styles when several fit; a pick made there arrives as a message. The question in ask_next is for the customer either way: ask it. Also records a decision about the order: a stop, an objection to the price or the date, or a request we do not offer. It belongs to the order's record, and the reply says what the order still needs.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "order_id": "<order_id>",
      "context": "<context>"
    },
    "name": "describe_order"
  }
}

Input Schema

NameRequiredDescriptionDefault
contextYesWhat the customer said, in their own words. Garment, color, size, quantity, print width in inches, placement, deadline — whatever is new. Unstructured prose is fine.
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, unless our app already shows it in the chat, 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, prices and minimums, say the one marked is_provisional is what we will use unless they choose, and call choose_style with the id they pick (or send "any" to describe_order to leave it to us).
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
mockup_changedNoTrue when mockup_views shows the design on the garment differently from the last time it was shown: a new garment, color, design, placement or width. Show the pictures again when it is true.
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. Changed4 schema fields changed
    • addedOutput schema / properties / garment / properties / size / description
      Added value: +"The size, or the size spread in the style's size order: \"2 S, 6 M, 7 L\". Sizes alone until their pieces are known."
    • addedOutput schema / properties / spec / properties / size / description
      Added value: +"The one size the order is in; null until a size is known, and when the order is spread across several."
    • addedOutput schema / properties / spec / properties / sizes
      Added value: +{
      +  "description": "The size spread: how the quantity splits across sizes. Complete once the pieces add up to quantity; get_options needs it complete.",
      +  "items": {
      +    "properties": {
      +      "quantity": {
      +        "description": "Pieces in this size; null until the customer says how many.",
      +        "type": [
      +          "integer",
      +          "null"
      +        ]
      +      },
      +      "size": {
      +        "type": "string"
      +      }
      +    },
      +    "required": [
      +      "size"
      +    ],
      +    "type": "object"
      +  },
      +  "type": "array"
      +}
    • addedOutput schema / properties / spec / required
      Added value: +[
      +  "sizes"
      +]
  2. Changed3 schema fields changed
    • changedOutput schema / properties / alternatives / items / properties / mockup_url / description
      Previous value: -"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."New value: +"An image address: show it as a picture where your client can, unless our app already shows it in the chat, never as text or as a link, and never describe it in place of the summary."
    • changedOutput schema / properties / mockup_url / description
      Previous value: -"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."New value: +"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, unless our app already shows it in the chat, never as text or as a link, and never describe it in place of the summary."
    • changedOutput schema / properties / mockup_views / items / properties / url / description
      Previous value: -"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."New value: +"An image address: show it as a picture where your client can, unless our app already shows it in the chat, never as text or as a link, and never describe it in place of the summary."
  3. Changed1 schema field changed
    • addedOutput schema / properties / mockup_changed
      Added value: +{
      +  "description": "True when mockup_views shows the design on the garment differently from the last time it was shown: a new garment, color, design, placement or width. Show the pictures again when it is true.",
      +  "type": "boolean"
      +}
  4. Changed5 schema fields changed
    • changedOutput schema / properties / alternatives / description
      Previous value: -"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)."New value: +"Present from the moment several styles fit until the customer picks, beside whatever ask_next asks: show all of them with their summaries, prices and minimums, say the one marked is_provisional is what we will use unless they choose, and call choose_style with the id they pick (or send \"any\" to describe_order to leave it to us)."
    • addedOutput schema / properties / alternatives / items / properties / minimum
      Added value: +{
      +  "description": "The minimum as the storefront words it (\"Minimum 10\", \"No minimum\"). Say it with the price.",
      +  "type": "string"
      +}
    • addedOutput schema / properties / alternatives / items / properties / minimum_quantity
      Added value: +{
      +  "description": "The fewest pieces the style is sold in.",
      +  "type": "integer"
      +}
    • changedOutput schema / properties / alternatives / items / properties / priced_at_quantity / description
      Previous value: -"The quantity the price is for: the order's, or 1 until the customer says how many. It drops at 12 and again at 24."New value: +"The quantity the price is for: the order's, or 1 until the customer says how many, or the style's minimum when that is more. It drops at 12 and again at 24."
    • changedOutput schema / properties / alternatives / items / required
      Previous value: -[
      -  "id",
      -  "name",
      -  "unit_price_cents",
      -  "priced_at_quantity",
      -  "rank",
      -  "summary",
      -  "is_provisional",
      -  "style"
      -]New value: +[
      +  "id",
      +  "name",
      +  "unit_price_cents",
      +  "priced_at_quantity",
      +  "minimum_quantity",
      +  "minimum",
      +  "rank",
      +  "summary",
      +  "is_provisional",
      +  "style"
      +]
  5. Changed18 schema fields changed
    • changedOutput schema / properties / chosen_option / properties / delivers_by / description
      Previous value: -"The date it arrives, YYYY-MM-DD."New value: +"The date free delivery arrives, YYYY-MM-DD."
    • changedOutput schema / properties / chosen_option / properties / delivery_days / description
      Previous value: -"Business days from now to the customer's door."New value: +"Business days from now to the customer's door with free delivery."
    • removedOutput schema / properties / chosen_option / properties / delivery_label
      Removed value: -{
      -  "description": "\"Free delivery\" or \"Rush delivery\"; standard shipping costs nothing, rush shipping is charged at checkout.",
      -  "type": "string"
      -}
    • addedOutput schema / properties / chosen_option / properties / meets_deadline / description
      Added value: +"Whether free delivery arrives by the customer's deadline."
    • addedOutput schema / properties / chosen_option / properties / rush_delivers_by
      Added value: +{
      +  "description": "The earliest date rush delivery arrives, YYYY-MM-DD; its shipping is priced at checkout, where the customer chooses the speed.",
      +  "type": [
      +    "string",
      +    "null"
      +  ]
      +}
    • addedOutput schema / properties / chosen_option / properties / rush_delivery_days
      Added value: +{
      +  "description": "Business days to the door with rush delivery; null when rush is no sooner.",
      +  "type": [
      +    "integer",
      +    "null"
      +  ]
      +}
    • addedOutput schema / properties / chosen_option / properties / rush_meets_deadline
      Added value: +{
      +  "type": [
      +    "boolean",
      +    "null"
      +  ]
      +}
    • removedOutput schema / properties / chosen_option / properties / speed
      Removed value: -{
      -  "enum": [
      -    "standard",
      -    "rush"
      -  ],
      -  "type": "string"
      -}
    • changedOutput schema / properties / chosen_option / required
      Previous value: -[
      -  "id",
      -  "method",
      -  "speed",
      -  "quantity",
      -  "unit_price_cents",
      -  "total_cents",
      -  "currency",
      -  "delivery_days",
      -  "delivers_by",
      -  "delivery_label",
      -  "summary"
      -]New value: +[
      +  "id",
      +  "method",
      +  "quantity",
      +  "unit_price_cents",
      +  "total_cents",
      +  "currency",
      +  "delivery_days",
      +  "delivers_by",
      +  "summary"
      +]
    • changedOutput schema / properties / options / items / properties / delivers_by / description
      Previous value: -"The date it arrives, YYYY-MM-DD."New value: +"The date free delivery arrives, YYYY-MM-DD."
    • changedOutput schema / properties / options / items / properties / delivery_days / description
      Previous value: -"Business days from now to the customer's door."New value: +"Business days from now to the customer's door with free delivery."
    • removedOutput schema / properties / options / items / properties / delivery_label
      Removed value: -{
      -  "description": "\"Free delivery\" or \"Rush delivery\"; standard shipping costs nothing, rush shipping is charged at checkout.",
      -  "type": "string"
      -}
    • addedOutput schema / properties / options / items / properties / meets_deadline / description
      Added value: +"Whether free delivery arrives by the customer's deadline."
    • addedOutput schema / properties / options / items / properties / rush_delivers_by
      Added value: +{
      +  "description": "The earliest date rush delivery arrives, YYYY-MM-DD; its shipping is priced at checkout, where the customer chooses the speed.",
      +  "type": [
      +    "string",
      +    "null"
      +  ]
      +}
    • addedOutput schema / properties / options / items / properties / rush_delivery_days
      Added value: +{
      +  "description": "Business days to the door with rush delivery; null when rush is no sooner.",
      +  "type": [
      +    "integer",
      +    "null"
      +  ]
      +}
    • addedOutput schema / properties / options / items / properties / rush_meets_deadline
      Added value: +{
      +  "type": [
      +    "boolean",
      +    "null"
      +  ]
      +}
    • removedOutput schema / properties / options / items / properties / speed
      Removed value: -{
      -  "enum": [
      -    "standard",
      -    "rush"
      -  ],
      -  "type": "string"
      -}
    • changedOutput schema / properties / options / items / required
      Previous value: -[
      -  "id",
      -  "method",
      -  "speed",
      -  "quantity",
      -  "unit_price_cents",
      -  "total_cents",
      -  "currency",
      -  "delivery_days",
      -  "delivers_by",
      -  "delivery_label",
      -  "summary"
      -]New value: +[
      +  "id",
      +  "method",
      +  "quantity",
      +  "unit_price_cents",
      +  "total_cents",
      +  "currency",
      +  "delivery_days",
      +  "delivers_by",
      +  "summary"
      +]
  6. Changed2 schema fields changed
    • changedOutput schema / properties / chosen_option / properties / delivery_label / description
      Previous value: -"\"Free delivery\" or \"Rush delivery\"; standard shipping costs nothing."New value: +"\"Free delivery\" or \"Rush delivery\"; standard shipping costs nothing, rush shipping is charged at checkout."
    • changedOutput schema / properties / options / items / properties / delivery_label / description
      Previous value: -"\"Free delivery\" or \"Rush delivery\"; standard shipping costs nothing."New value: +"\"Free delivery\" or \"Rush delivery\"; standard shipping costs nothing, rush shipping is charged at checkout."
  7. First observed

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false and openWorldHint=false, so the mutating-but-safe profile is covered structurally. The description adds genuine context beyond that — the detail is attached to the order's record, the customer sees the design update on the garment when it changes, and the reply reports what the order still needs — but it does not say whether a call replaces or appends to prior detail, which matters for a non-destructive write.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The text is long and loosely structured, mixing purpose, UI rendering behavior, message-routing notes, and decision recording across run-on sentences. It repeats itself — 'reports what is still needed' near the opening and 'the reply says what the order still needs' at the end — and the sentence about ask_next's question being for the customer either way is unclear without the referenced tool's definition.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With an output schema present, the description need not explain the reply structure, and annotations plus full schema coverage remove most other burdens. What remains missing is the crucial operational relationship to ask_next (an unknown tool the description tells the agent to obey) and whether repeated calls accumulate or overwrite.

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 both parameters (context, order_id) are already fully documented in the schema. The description adds little param-specific meaning beyond reinforcing that context is free-form customer prose; the note about ask_next's question being for the customer is not parameter semantics.

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 gives a specific verb (records) and a concrete resource (free-form detail about what the customer wants: a correction, a paragraph, a design change), plus it separately names decision-type content (a stop, a price/date objection, an unavailable request). It partially distinguishes itself from structured siblings by noting that in app-rendering clients 'a pick made there arrives as a message,' but that sentence is oblique and references ask_next, which is not in the sibling set, so the boundary with choose_option/choose_style is only half drawn.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is explicit when-to-use guidance: 'Call it each time the customer gives a new detail.' However, there is no when-not-to-use guidance and no named alternative — the closest thing is the implied case where a pick from the rendered app already arrives as a message, which the agent has to interpret.

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