Skip to main content
Glama

get_orders

Read-only

List orders for one or more user addresses, paginated.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "user_addresses": "<user_addresses>"
    },
    "name": "get_orders"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoPage size
cursorNoCursor from a previous response's `nextCursor`
user_addressesYesUser addresses (up to 20), each encoded for its own chain

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=true and openWorldHint=true, so the safety profile is covered. The description adds only the word 'paginated', without explaining ordering, whether results are truncated per address, or how paging interacts with the multi-address input. That is modest added value beyond structured fields.

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, and the pagination note is placed where it is useful. It is efficient, though so short that it borders on under-specification rather than deliberate density.

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?

The tool is a simple read-only list with only three well-documented parameters, so the burden is light, and annotations cover safety. However, with no output schema, the description should say something about the returned shape (an order collection plus a next cursor) and nothing does.

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%, including limit, cursor, and the up-to-20 addresses constraint, so the schema already carries parameter meaning. The description's 'one or more user addresses' and 'paginated' restate rather than extend that, which is the baseline-3 case when the schema does the heavy lifting.

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?

States a specific verb and resource ('List orders') plus a scoping constraint ('for one or more user addresses'), which implicitly distinguishes it from the singular sibling get_order. It stops short of naming any sibling, but the bulk-listing purpose is unambiguous.

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: nothing says whether to pick this over get_order, wait_for_order, or how it relates to create_order/quote_and_create flows. The phrase 'one or more user addresses' hints at batch retrieval, but the agent must infer that from the phrasing rather than being told.

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