Skip to main content
Glama

List orders

list_orders
Read-onlyIdempotent

Retrieve your company's orders, newest first and paginated, to review order status and history; users without company-wide permission see only their own orders.

Instructions

Orders for the buyer's company, newest first, paginated. Users without company-wide order permission only see their own orders.

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
pageNo
statusNo
page_sizeNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

B3/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world, so the safety profile is covered. The description adds genuinely useful context beyond them: results are sorted newest-first, paginated, and permission-scoped to the caller's company or own orders. It does not describe the response shape or page 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?

Two short sentences, zero padding, and the core scope is front-loaded. It could be slightly sharper by naming the sort/pagination parameters, but nothing is wasted.

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 three-optional-parameter read tool with rich annotations and no output schema, the description is adequate but incomplete: it omits the status filter and the pagination bounds (page_size max 20, page max 10000) that an agent needs to call it well.

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%, so the description must carry parameter meaning, and it only implies that pagination exists ('paginated'). It says nothing about the page, page_size, or status filter parameters, their defaults, or the meaning of the status enum values.

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 resource (orders) with scope (the buyer's company), ordering (newest first), and pagination. It is clearly a list operation, though it does not explicitly distinguish itself from siblings like get_order_status that deal with single orders.

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 explicit guidance on when to use this versus get_order_status or other order-related siblings. The permission note ('users without company-wide order permission only see their own orders') is a visibility behavior rather than a when-to-use cue, leaving usage to inference.

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