Skip to main content
Glama

list_store_orders

Read-onlyIdempotent

List order status, totals and refunds for the approved business. Amounts are minor units in each order's currency.

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

Input Schema

NameRequiredDescriptionDefault
offsetNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.3/5.0
Behavior3/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 fully covered and the description is not contradicted. The description does add genuinely useful behavioral context not in the annotations: monetary amounts are returned as minor units in each order's own currency, which prevents a downstream formatting error. However it says nothing about pagination, page size, or result caps despite exposing an offset parameter.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two tight sentences with zero filler; the primary purpose is front-loaded and the unit-of-account caveat follows immediately. Every clause carries information an agent would otherwise get wrong.

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?

With no output schema, the description does the right thing by naming the returned fields (status, totals, refunds) and the currency convention, so return semantics are mostly covered. It is incomplete for a paginated list endpoint: an agent cannot tell from the definition how many orders come back per call or whether offset must be advanced manually.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% for the single 'offset' parameter, so the description carries the full burden and fails to address it — no mention of paging, page size, the default of 0, or the 100000 ceiling. The only parameter-adjacent information given is about output currency units, not about how to drive the input.

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 ('List') with a concrete resource set ('order status, totals and refunds') scoped to 'the approved business'. It is clearly a bulk-listing tool, which distinguishes it from a single-record sibling like get_store_order, but it never names or explicitly contrasts with any sibling.

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 by the verb 'List' plus the business scoping clause; there is no statement of when to use this versus get_store_order or get_store_order_reconciliation, and no exclusions or prerequisites. An agent can infer it is the collection view, but must make that inference itself.

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