Skip to main content
Glama

Your orders

list_orders
Read-onlyIdempotent

Lists the signed-in account's orders, newest first, as its Orders screen shows them: reference, date, ship-to state, products, the reading recorded for each, and on the Record plan the lots tied and whether consent was recorded. A test key lists test orders. Does not count as a lookup.

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

Input Schema

NameRequiredDescriptionDefault
showNoOptional filter: all, held, restricted (restricted or conditions), lot_unknown, no_consent, after_sale.
limitNoHow many orders. Default 25.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/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 the safety profile is handled. The description adds real behavioral context on top: newest-first ordering, plan-dependent field variation (lots tied and consent recording only on the Record plan), and that a test key returns test orders. It stops short of covering pagination behavior or ordering guarantees beyond 'newest first'.

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?

Three sentences, front-loaded with the verb and the returned shape, with no filler. The enumerated field list is long but each item earns its place by explaining the return payload in the absence of an 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?

With no output schema, the description carries the return-value burden and does so by listing the fields returned, including plan-conditional ones and test-key behavior. Missing only edge details such as ordering ties or how limits interact with large result sets, which is minor for a two-parameter read tool.

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 description coverage is 100% and the show enum values are self-documented with a default limit of 25, so the baseline is 3. The description mentions 'held', 'restricted', consent and lot conditions implicitly through the returned fields, but adds no explicit guidance on what each filter value selects.

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?

Opens with a specific verb and resource ('Lists the signed-in account's orders') and enumerates what comes back (reference, date, ship-to state, products, readings, lot/consent data on the Record plan). The closing note 'Does not count as a lookup' distinguishes it from the lookup-style siblings without needing their schemas.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is implied rather than stated: the tool is scoped to the signed-in account's orders, and the plan/test-key conditions hint at context, but the description never says when to prefer this over get_order or list_audits, nor when a filter should be applied.

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