Skip to main content
Glama

Get My Orders

get_my_orders
Read-only

The caller's orders on XP, newest first: status, fulfilment status, delivery method, in-hand date, event, seats and the all-in total in dollars -- 'where is my order?', 'when do my tickets arrive?'. get_order_status reads one order by its order_uuid and get_my_tickets lists tickets already delivered; offers the caller placed are in get_my_offers and listings they are selling in list_my_listings. Requires sign-in.

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": "get_my_orders"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoHow many recent orders to return, 1-50. Defaults to 20.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, openWorldHint=false, so the safety profile is covered. The description adds genuinely useful non-schema context: it requires sign-in and returns results newest-first. It does not discuss pagination beyond the limit default or how large result sets behave, which holds it below a 5.

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?

Front-loaded with the scope and ordering, then the field list, then intent phrasing, then alternatives -- a logical progression with no filler. The field enumeration is dense but each item earns its place by telling the agent what it will receive.

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-optional-param read tool with annotations and an output schema, this is close to complete: scope, ordering, auth requirement, and sibling routing are all present. Return-field semantics could lean on the output schema rather than being restated, so the description does slightly more than needed rather than less.

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?

Only one parameter (limit), and schema description coverage is 100% with the range 1-50 and default 20 already documented in the schema. The description adds nothing about the limit beyond implying recency ordering ('newest first'). Baseline 3 is appropriate since the schema does the work.

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 verb and resource ('The caller's orders on XP'), enumerates the fields returned (status, fulfilment status, delivery method, in-hand date, event, seats, all-in total in dollars), and pins the ordering ('newest first'). This is clearly distinguishable from get_order_status (single order) and get_my_tickets (already-delivered tickets).

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?

Anchors usage to concrete user intents ('where is my order?', 'when do my tickets arrive?') and explicitly routes to alternatives with their distinguishing conditions: get_order_status for one order by order_uuid, get_my_tickets for delivered tickets, get_my_offers for offers placed, list_my_listings for listings being sold. An agent can pick the right tool without opening other schemas.

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