Skip to main content
Glama

Moqway

List orders

list_orders
Read-onlyIdempotent

The buyer's recent orders, newest first, optionally by status.

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
limitNo
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 readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered. The description adds useful behavior beyond that (newest-first ordering, buyer-scoped results, optional status filter), but says nothing about how 'recent' is bounded, how results are paginated beyond `limit`, or what a caller sees when no orders match.

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 compact sentence with the ordering constraint front-loaded and no filler. It could add the `limit` semantics at negligible cost, so it is lean to the point of under-specification.

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?

A simple read-only list tool with rich annotations and no output schema, so low burden overall. Still, with no output schema the description could say what an order record looks like or that results are truncated by `limit`, and it leaves the `limit` parameter entirely unexplained.

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. It clarifies that `status` filtering is optional but never mentions `limit` at all — not the default of 20, the max of 50, nor what happens if it is omitted. One of two parameters is effectively undocumented in prose.

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?

Names a specific verb+resource (list orders) and adds meaningful scope: the buyer's own orders, sorted newest first, with optional status filtering. It does not distinguish this from siblings like get_order (single order) or search_products, 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?

'Recent orders, optionally by status' implies the browsing use case, but there is no explicit when-to-use guidance, no statement of when to prefer get_order for a specific order, and no exclusions. Usage is inferable rather than stated.

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