Skip to main content
Glama

List my orders

list_orders
Read-only

List your owner's orders, newest first, a page at a time: order_id, item, amount, status and created_at, orders waiting for approval included (get_order for one in full). Pass next_before as before for the next page; it is null on the last.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "limit": 10,
      "before": "ord_exampleexampleexample2"
    },
    "name": "list_orders"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoHow many (default 20).
beforeNonext_before of the page before; leave out for the first page.
passport_tokenNoYour amp_ token, only if you have no app sign-in and cannot send a header.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / before / description
      Previous value: -"next_before of the page before."New value: +"next_before of the page before; leave out for the first page."
  2. Changed2 schema fields changed
    • addedInput schema / examples
      Added value: +[
      +  {
      +    "before": "ord_exampleexampleexample2",
      +    "limit": 10
      +  }
      +]
    • changedInput schema / properties / passport_token / description
      Previous value: -"Your amp_ token, only if your app has no sign-in and cannot send it as an Authorization header."New value: +"Your amp_ token, only if you have no app sign-in and cannot send a header."
  3. Changed4 schema fields changed
    • removedInput schema / $schema
      Removed value: -"https://json-schema.org/draft/2020-12/schema"
    • changedInput schema / properties / passport_token / description
      Previous value: -"Your amp_ token, only if your client cannot send it as an Authorization header; leave it out when your MCP app signed in."New value: +"Your amp_ token, only if your app has no sign-in and cannot send it as an Authorization header."
    • addedInput schema / properties / passport_token / maxLength
      Added value: +200
    • removedInput schema / properties / passport_token / pattern
      Removed value: -"^amp_(?:s_)?[A-Za-z0-9_-]{43}$"
  4. Added

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, destructiveHint=false and openWorldHint=false, so safety is covered structurally. The description adds real behavior beyond that: newest-first ordering, page-at-a-time retrieval, inclusion of orders pending approval, and the null termination signal on the last page. It omits auth specifics, but the schema's passport_token field already covers that.

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?

A single dense sentence front-loads what the tool returns, then the sibling pointer, then pagination mechanics; every clause carries information. The parenthetical and semicolon make it slightly run-on for a reader skimming, but nothing is wasted.

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?

There is no output schema, yet the description enumerates the returned fields, their order, and how pagination terminates, which is exactly what an agent needs to consume results. Defaults and bounds live in the schema where they belong, so nothing material is missing.

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 100%, so the baseline is 3. The description earns more by linking the input parameter to the output value: "Pass next_before as before for the next page; it is null on the last" explains a relationship the schema cannot express, since the schema only says "next_before of the page before."

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 your owner's orders"), plus ordering ("newest first"), pagination ("a page at a time"), and the exact fields returned. It explicitly separates itself from get_order ("get_order for one in full"), so an agent can choose between the siblings without opening either 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 clear context (browsing orders, including those awaiting approval) and names the alternative for the single-item case. It does not state when not to use it or whether any filtering exists, which keeps it 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.