Skip to main content
Glama

RushOrderTees

My orders

my_orders
Read-only

Lists the signed-in customer's orders with us, open and paid, each with its status. Needs the customer to be signed in; if they are not, your client will ask them to. Applies when the customer asks what they have with us, wants to pick up a saved order, or asks where an order is.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "my_orders"
  }
}

Input Schema

NameRequiredDescriptionDefault
includeNoWhich orders to list: everything (the default), only open unpaid ones, or only paid ones.

Output Schema

NameRequiredDescriptionDefault
ordersYesEvery order on this account, open and paid, latest activity first.
next_callYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedOutput schema / properties / orders / items / properties / progress
      Added value: +{
      +  "description": "For a paid order, each step from paid to delivered and whether it is done, current or upcoming; empty for an open or canceled order. Clients that render our order status widget already show it.",
      +  "items": {
      +    "properties": {
      +      "label": {
      +        "type": "string"
      +      },
      +      "state": {
      +        "enum": [
      +          "done",
      +          "current",
      +          "upcoming"
      +        ],
      +        "type": "string"
      +      }
      +    },
      +    "required": [
      +      "label",
      +      "state"
      +    ],
      +    "type": "object"
      +  },
      +  "type": "array"
      +}
    • changedOutput schema / properties / orders / items / required
      Previous value: -[
      -  "order_id",
      -  "status",
      -  "label",
      -  "paid",
      -  "expired",
      -  "summary",
      -  "still_needed",
      -  "has_artwork",
      -  "currency",
      -  "last_activity_at"
      -]New value: +[
      +  "order_id",
      +  "status",
      +  "label",
      +  "paid",
      +  "expired",
      +  "summary",
      +  "still_needed",
      +  "has_artwork",
      +  "currency",
      +  "last_activity_at",
      +  "progress"
      +]
  2. Changed3 schema fields changed
    • changedOutput schema / properties / orders / items / properties / label / description
      Previous value: -"The status in words a customer can read. A paid order reads \"Paid, in production\" until it ships."New value: +"The status in words a customer can read, such as \"Order received\" or \"In production\"."
    • addedOutput schema / properties / orders / items / properties / reading
      Added value: +{
      +  "description": "For a paid order, what its status means right now, such as \"Approval needed: check your email from RushOrderTees\". Tell the customer.",
      +  "type": [
      +    "string",
      +    "null"
      +  ]
      +}
    • changedOutput schema / properties / orders / items / properties / status_url / description
      Previous value: -"For a paid order. Show it to the customer as one link labeled \"Track your order\", not as a bare address."New value: +"For a paid order. Show it to the customer as one link labeled \"Order status\", not as a bare address: share this link with anyone who should follow the order."
  3. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already supply readOnlyHint=true and openWorldHint=false, so safety is covered; the description adds the real behavioral fact an agent needs — the call requires an authenticated customer and the client will prompt for sign-in if absent. It says nothing about paging or result volume, but the output schema exists to carry return shape.

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?

Three short sentences, each doing distinct work: what it returns, the auth precondition with its fallback behavior, and the routing triggers. No repetition of the title and no filler.

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?

For a one-optional-param read tool with an output schema and full annotations, the description covers purpose, auth flow, and activation context — nearly everything needed to invoke it. The only gap is that it doesn't distinguish listing from fetching one order's details, which matters given a describe_order sibling.

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 enum's three values are fully documented in the schema, so the baseline is 3. The description's 'open and paid' phrasing loosely parallels the include filter but adds no format or default detail beyond what the schema already states.

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 verb and resource ('Lists the signed-in customer's orders') plus scope ('open and paid, each with its status'), which clearly separates it from a single-order lookup like describe_order. It stops short of naming any sibling explicitly, so an agent must infer the boundary from the plural 'orders' framing.

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?

Gives concrete when-to-use triggers: the customer asking what they have, wanting to pick up a saved order, or asking where an order is. There are no when-not conditions and no named alternatives (e.g. for a single order's details), which keeps it below 5.

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