clover-mcp

list_orders

Read-only

List orders by date range or payment state, optionally selecting specific fields. Read-only; customer card data is never included.

Instructions

List orders within an optional date window and/or state filter (default: today, limit 50).

state: open | paid | refunded | partially_refunded (omit for all states). Customer card data is never included. This tool is read-only. fields: optional list of field names to keep (narrows the response; cannot widen past the allowlist).

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

Name	Required	Description	Default
`limit`	No
`state`	No
`fields`	No
`date_to`	No
`date_from`	No

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.7.0Aug 7, 2026

TDQS

A4.4/5.0

Behavior5/5

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

Even though readOnlyHint=true exists, the description reinforces read-only behavior and adds unique context: 'Customer card data is never included' and the field narrowing constraint 'cannot widen past the allowlist'. This goes beyond the annotation and informs the agent of privacy and response-shaping behavior.

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?

The description is three sentences, front-loaded with the primary purpose, and each sentence adds necessary detail. No filler or repetition.

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

Completeness4/5

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

The description covers main behavior, defaults, safety, and field selection. An output schema exists, so return values need no explanation. Minor gaps include date format and a more explicit mention of how limit behaves, but overall the tool is well described for its complexity.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With 0% schema description coverage, the description compensates by explaining the state parameter with its enum values, the fields parameter's narrowing behavior, and the concept of a date window. It partially explains limit via 'limit 50' and mentions date_from/date_to generically, but does not specify formats or full limit semantics.

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 opens with a specific verb and resource: 'List orders' and clarifies the scope with 'optional date window and/or state filter'. It distinguishes itself from sibling tools like list_open_orders by covering all states ('omit for all states') and from get_order by being a list operation.

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?

The description gives clear context on defaults (today, limit 50) and filters, but it does not explicitly state when to use this tool over siblings like list_open_orders or when not to use it. The usage is implied rather than stated with exclusions.

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

Deploy Server