Skip to main content
Glama

order_list

Read-onlyIdempotent

Orders you own, plus orders this machine holds tokens for.

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

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum to return (default 20).
statusNoactive, all, or a status.

Output Schema

NameRequiredDescriptionDefault
okYes
dataNo
errorNo
summaryNo
warningsNo
next_actionsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so safety is covered. The description's one real contribution is the visibility model ('you own' plus 'this machine holds tokens for'), which is behavior an agent could not get from annotations or schema. It stays silent on pagination behavior, ordering, and result size beyond the schema's limit default.

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 short sentence with no filler, and the scope qualifier is front-loaded. The phrasing 'this machine holds tokens for' is slightly opaque but is the only place that information appears, so it earns its space.

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?

Output schema exists and annotations are rich, so the description needn't explain return values or safety. For a two-parameter read-only list tool, the description supplies the one non-obvious fact (which orders are visible) and leaves the rest to structured fields. It could be stronger by clarifying status semantics or result ordering, but nothing essential for invoking 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 description coverage is 100% and both parameters (limit with a default of 20, status accepting active/all/a status) are documented inline. The description adds no meaning about how status filtering interacts with the owned-vs-token-held scope, so it earns the baseline rather than more.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states the specific set of resources returned: orders the caller owns plus orders this machine holds tokens for. That scope statement distinguishes it from a single-order tool like order_show without naming it. The verb is only implied by the name 'order_list', which keeps it just short of a 5.

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

Usage Guidelines2/5

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

There is no when-to-use guidance, no conditions for choosing this over order_show or order_events, and no mention of prerequisites or how token-held vs owned orders differ in practice. The only implied usage is 'this is the collection endpoint', which an agent must infer.

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