Medusa MCP Server

GetOrders

Retrieve customer orders with filtering, sorting, and pagination options to manage order data efficiently.

Instructions

Retrieve the orders of the logged-in customer. The orders can be filtered by fields such as id. The orders can also be sorted or paginated.

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": "GetOrders"
  }
}

Input Schema

Name	Required	Description	Default
`fields`	No
`offset`	No
`limit`	No
`order`	No
`id`	No
`$and`	No
`$or`	No
`status`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedAug 18, 2025

TDQS

C2.7/5.0

Behavior2/5

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

No annotations are provided, so the description carries the full burden. It states the tool retrieves orders for the logged-in customer, implying authentication is required, but doesn't disclose behavioral traits like rate limits, error conditions, response format, or whether it's read-only. The description is minimal and lacks critical operational details.

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?

The description is concise and front-loaded, stating the core purpose in the first sentence. The second sentence adds filtering, sorting, and pagination details efficiently. No wasted words, though it could be more structured with bullet points for clarity.

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

Completeness2/5

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

Given the complexity (8 parameters, no annotations, no output schema), the description is incomplete. It lacks details on authentication requirements, response format, error handling, and full parameter usage. For a retrieval tool with multiple filtering options, more context is needed to guide effective use.

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?

The input schema has 8 parameters with 0% description coverage. The description mentions filtering by 'id' and capabilities for sorting and pagination, but it doesn't explain the semantics of parameters like 'fields', '$and', '$or', or 'status', nor does it detail how sorting or pagination work. It adds some value but doesn't compensate for the low schema coverage.

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?

The description clearly states the tool's purpose: 'Retrieve the orders of the logged-in customer.' It specifies the resource (orders) and scope (logged-in customer), though it doesn't explicitly differentiate from sibling tools like GetOrdersId, which likely retrieves a single order by ID.

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

Usage Guidelines2/5

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

The description provides no guidance on when to use this tool versus alternatives. It mentions filtering, sorting, and pagination but doesn't compare to sibling tools like GetOrdersId for single-order retrieval or other list tools like GetProducts. Usage context is implied but not explicit.

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

Deploy Server