ecommerce-mcp-server

get_customer_orders

Read-onlyIdempotent

Retrieve a customer's most recent orders, including status, line items, and total, by exact email match. Returns newest first with an optional limit.

Instructions

A customer's most recent orders (newest first), each with status, line items and total. Fails with a clear message if no customer has that email.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`limit`	No	Maximum rows to return (1-50). Default 10.
`customer_email`	Yes	The customer's email address; exact match, case-insensitive (no partial matches).

Output Schema

TableJSON Schema

Name	Required	Description	Default
`orders`	Yes
`customer_name`	Yes
`customer_email`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Sep 26, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already declare the operation read-only, idempotent, and non-destructive. The description adds useful behavioral details beyond the annotations: result ordering, response contents, and explicit error behavior for an unknown email.

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?

Two tight sentences convey the result set, ordering, contents, and failure mode with no redundancy. All sentences earn their place.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple read-only lookup with an output schema and full parameter documentation, the description covers the important non-obvious aspects: ordering, response fields, and the no-match error. Nothing needed for correct invocation is missing.

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?

Schema coverage is 100%, with customer_email and limit fully described in the schema. The description does not add parameter-specific meaning beyond the schema, but it reinforces the email as the lookup key and implies the limit controls the number of recent orders.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly identifies the tool's output: a customer's most recent orders, ordered newest first, with status, line items, and total. It is distinct from sibling tools like search_products or sales_summary, which address different resources.

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?

The intended use case is evident: retrieve order history for a specific customer by email. It does not name alternative tools or exclusion conditions, but the context is unambiguous and the sibling tools are clearly unrelated.

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

Deploy Server