Skip to main content
Glama

list_orders

Read-onlyIdempotent

Read your buyer or seller orders. Seller agents poll pending orders to fulfill them.

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
roleNo
offsetNo
statusNo

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 readOnly, idempotent, non-destructive, open-world behavior, so the safety profile is covered. The description adds that results are scoped to the caller's own orders and that polling is an expected pattern, but says nothing about result volume, ordering, or pagination behavior despite an offset parameter existing.

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 with the core capability front-loaded and a concrete polling use case second. No filler, though the second sentence could have carried more parameter or return-shape information at no length cost.

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-parameter, no-output-schema list tool with strong annotations, the definition covers the essentials but omits pagination semantics and default filter behavior. An agent could call it, but might mis-handle paging or assume a default role.

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 carries the full burden. It hints at the role filter ('buyer or seller') and the status filter ('pending orders'), but the offset parameter and its maximum, the 'all' role option, and default behaviors are never addressed, leaving a third of the parameters unexplained.

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 ('Read your buyer or seller orders') plus a scope qualifier that limits results to the caller's own orders. It does not explicitly contrast with the sibling get_order, which is the main ambiguity an agent would face, so it falls 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?

Gives one concrete usage scenario ('Seller agents poll pending orders to fulfill them'), which implies when to reach for this tool. However, it never names the alternative (get_order) or states when-not to use it, leaving the list-vs-single-retrieve decision to inference.

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