Skip to main content
Glama

List my orders

list_my_orders
Read-onlyIdempotent

The connected person's own order history at WaitApp venues, newest first. Each order has its venue, code, status, total, type, when it was placed and what was ordered: every item with its quantity, price and chosen choices. Items carry menuItemId and selectedOptions in the form draft_delivery_order accepts. Deliveries also show the address, delivery fee and stage. A kitchen and a bar order placed together are one entry. Filter by venue, status, text (an item or venue name) or date, and page back with nextBefore. Only this person's own orders are returned.

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_orders"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
queryNoAn item name or venue name, e.g. burger or Social
sinceNoOnly orders placed on or after this date, e.g. 2026-09-01
beforeNoOnly orders placed before this time. Pass nextBefore from the previous page
statusNoe.g. pending, accepted, preparing, ready, served, cancelled
restaurantIdNoOnly orders at this venue

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already cover the safety profile, and the description layers on substantial behavior beyond them: newest-first ordering, that a kitchen+bar pair collapses into one entry, delivery-specific fields (address, fee, stage), and that item fields are shaped to feed draft_delivery_order. That last point is a genuinely useful cross-tool contract.

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?

The scope and ordering are front-loaded and the return-shape detail is dense but earns its place given there is no output schema. Slightly long, with the delivery and item-shape sentences packed tightly, but no filler.

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 full return-value burden and delivers: per-order fields, item structure, delivery-specific fields, and order aggregation rules. An agent knows both how to call it and what comes back.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 83%, so the schema carries most of the burden, but the description adds real meaning by glossing 'text' as item-or-venue name and tying 'before' to nextBefore paging. It does not clarify the since/before precedence or the limit cap beyond schema defaults.

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 ('List... order history'), names the scope ('the connected person's own... newest first') and explicitly excludes other people's orders. An agent can distinguish it from track_order or cancel_order without opening any 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?

Enumerates the available filters (venue, status, text, date) and explains the paging mechanism ('page back with nextBefore'), giving clear browsing context. It stops short of naming sibling alternatives such as track_order when a single order's live state is wanted.

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