Skip to main content
Glama

Get Order Status

get_order_status
Read-only

One of the caller's orders on XP by order_uuid (from buy_tickets or get_my_orders) -- 'did that go through?'. Returns status, fulfilment status, delivery method, in-hand date, event, seats and the all-in total in dollars. The recent list is in get_my_orders. Requires sign-in.

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_uuid": "<order_uuid>"
    },
    "name": "get_order_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
order_uuidYesThe order_uuid returned by buy_tickets (or listed by get_my_orders).

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so safety is covered; the description adds the non-obvious prerequisite 'Requires sign-in' and the currency framing of the total ('all-in total in dollars'). The enumerated return fields add less value since an output schema exists, and nothing is said about errors for invalid/foreign uuids.

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?

One compact passage with the resource and key front-loaded, followed by return contents and the list-sibling pointer. Tight overall, though the opening is a sentence fragment and the return-field enumeration partly duplicates the output schema.

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 single-parameter read tool with annotations and an output schema, the description covers the key prerequisite (sign-in), the id source, and scope. What remains unstated — behavior for a missing or foreign order_uuid — is minor but would help an agent handle failure cases.

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 parameter's own description already states it comes from buy_tickets or get_my_orders, so the description's provenance note is largely duplicative. It adds no format, validation, or ownership constraints beyond 'the caller's orders', which is the minimum over the schema baseline.

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?

States a specific resource and scope: 'One of the caller's orders on XP by order_uuid', and immediately disambiguates from the list sibling ('The recent list is in get_my_orders'). An agent knows exactly what it retrieves and how it differs from get_my_orders and buy_tickets without opening a schema.

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 a concrete usage scenario ('did that go through?'), tells the caller where to obtain the required order_uuid (buy_tickets or get_my_orders), and implicitly routes listing needs to get_my_orders. No explicit when-not or failure-mode guidance (e.g., what happens for an unknown uuid), so it falls short of a full 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