Skip to main content
Glama

list_commerce_orders

list_commerce_orders

List commerce orders where the authenticated wallet is buyer or seller.

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

Input Schema

NameRequiredDescriptionDefault
idNoOptional order id.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full burden. It does disclose two meaningful behaviors: authentication context (an authenticated wallet is required) and result filtering (only orders where that wallet is buyer or seller). It says nothing about pagination, limits, ordering, or what fields come back, which is a real gap for a list tool with no output schema.

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?

One front-loaded sentence with no filler; the scope constraint arrives immediately after the resource. Nothing could be cut without losing information.

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 one-optional-parameter read tool this is close to sufficient, and the buyer-or-seller scope is the key detail an agent needs. However, with no annotations and no output schema, the description should compensate by saying something about result shape or pagination, and it does not.

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?

There is a single optional 'id' parameter with 100% schema description coverage, so the schema already documents it. The description adds no meaning about what passing an id does (lookup vs. filter) and never acknowledges the parameter, so baseline 3 applies.

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 (List) and resource (commerce orders) plus a scoping condition: only orders where the authenticated wallet is buyer or seller. This distinguishes it reasonably well from list-shaped siblings like list_invoices and list_payments, though it doesn't explicitly name any alternative.

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' and the buyer/seller scope; there is no statement of when to use this versus list_invoices, list_payments, or get_activity, and no exclusions or prerequisites beyond the implicit wallet authentication.

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