Skip to main content
Glama

List orders

get_orders

Lists an agent's orders and each piece's status—scheduled, sending, done, failed, or cancelled—with an option to show only open orders.

Instructions

Lists this agent's orders with the status of every piece (scheduled, sending, done, failed, cancelled).

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

Input Schema

NameRequiredDescriptionDefault
onlyOpenNoOnly orders still scheduled or routing

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

B3.4/5.0
Behavior3/5

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

With no annotations supplied, the description must carry the behavioral burden. It does convey that this is a read operation scoped to the calling agent and that each order exposes per-piece statuses, but it says nothing about permissions, ordering, pagination, or result size limits.

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 front-loaded sentence with no filler. The parenthetical status list is informative rather than redundant, though it slightly lengthens an otherwise tight statement.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple one-parameter read tool this covers purpose and scope adequately, but with no output schema and no annotations, the description leaves return shape, ordering, and pagination entirely unexplained. It is minimally sufficient rather than complete.

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 single optional parameter onlyOpen is already documented in the schema as limiting to orders "still scheduled or routing." The description adds no further meaning about that flag, so the baseline 3 applies.

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 uses a specific verb ("Lists") and resource ("orders") and scopes it to "this agent's orders," which distinguishes it from account-level siblings like get_balance or get_fills. It also enumerates the possible statuses, but it doesn't explicitly name a sibling alternative, so it stops 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 Guidelines3/5

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

Usage is only implied: the agent can infer this is the tool for viewing its own orders rather than cancelling (cancel_order) or placing them (route_order). There is no explicit when-to-use/when-not-to-use guidance and the sibling tools are never referenced.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.