Skip to main content
Glama

customer_orders

Read-onlyIdempotent

List a customer's recent orders using their customer ID; first call find_customer to obtain the ID. Use limit to control result count.

Instructions

Lista os pedidos mais recentes de um cliente (use find_customer antes para obter o ID).

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "customer_id": "<customer_id>"
    },
    "name": "customer_orders"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
customer_idYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, and non-destructive, so the safety profile is covered. The description adds the useful workflow prerequisite and a 'most recent' ordering claim, but does not define what 'most recent' means or how the result set is bounded.

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?

A single sentence with the action front-loaded and the prerequisite in parentheses; no wasted wording.

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?

An output schema exists, so return values need no explanation, and the prerequisite is covered. However, the limit parameter and the ordering semantics of 'most recent' are left undefined for a tool whose schema has no descriptions.

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 the burden. It explains that customer_id must come from find_customer, but says nothing about the limit parameter's default of 10 or its effect on the listing.

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: listing a customer's most recent orders. The plural/recency framing implicitly separates it from the singular sibling get_order, and it names find_customer as a related tool, though it does not explicitly contrast with get_order.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives an explicit prerequisite chain: call find_customer first to obtain the ID. It stops short of stating when to prefer this over get_order or how to page through results, so no exclusions are offered.

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