Skip to main content
Glama

List my recent orders

list_my_recent_orders
Read-onlyIdempotent

Returns recent orders on the customer's account, with order number, total, status, effective date, and what has been refunded. Use when the user asks "what did I buy recently?", "show me my last order", "what was my last invoice for?", "was I refunded?". Each order carries total (what was charged), refunded (what has since gone back to the customer, 0 when nothing has), and net (total minus refunded). An order's status stays "Activated" after a refund, so read refunded, not status, to answer whether money went back. Read-only.

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

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum number of orders to return (default 5, max 25).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior5/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so safety is covered; the description goes beyond that with non-obvious domain semantics: `status` stays 'Activated' after a refund, so `refunded` must be read instead. That prevents a specific, likely misinterpretation and defines total/refunded/net precisely.

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?

Front-loaded with what is returned, then trigger phrases, then the field semantics that matter most. Every sentence supplies either routing information or a non-obvious interpretation rule; nothing is redundant with the schema or annotations.

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?

With no output schema, the description takes on the job of naming return fields and explaining total/refunded/net and the misleading status value, which it does fully. For a one-parameter read-only listing tool, nothing an agent needs to call or interpret it correctly is missing.

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 single `limit` parameter already documents its default (5) and max (25), so the description adds no parameter-level meaning. This is the expected baseline when the schema carries the load.

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 ('Returns recent orders on the customer's account') and enumerates the fields returned (order number, total, status, effective date, refunded), so an agent knows exactly what it gets. The orders resource is distinct from every sibling (backups, cases, domains, hosting, migrations), so no further differentiation is needed.

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 trigger phrasings ('what did I buy recently?', 'show me my last order', 'was I refunded?') that map directly to user intent, which is strong positive guidance. It does not state exclusions or point to an alternative tool for related queries (e.g., invoice-specific lookups), so it stops short of a full when/when-not treatment.

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