Skip to main content
Glama
Minimax MCP Server

Minimax MCP Server

by chehcore

List Minimax Orders

minimax_list_orders
Read-onlyIdempotent

Lists sales and purchase orders with filters for type, customer, status, and lifecycle dates; returns paginated JSON with has_more.

Instructions

List sales and purchase orders with filters for type, customer, status and the date of each life-cycle step.

Returns: str: JSON SearchResult with has_more.

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": {
      "params": "<params>"
    },
    "name": "minimax_list_orders"
  }
}

Input Schema

NameRequiredDescriptionDefault
paramsYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so the safety profile is covered by structured data. The description's only added behavioural fact is that results come back as a JSON SearchResult carrying has_more, which signals pagination; it says nothing about page_size limits, default organisation fallback, or result ordering, which matters for a query with 21 optional filters.

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?

Two short, front-loaded sentences with no filler; the filter summary comes first and the return note second. It is arguably too terse for a 21-parameter query tool, but nothing written is wasted.

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 the description need not enumerate return fields, and the stated has_more flag is a useful pointer. For a tool with this many optional filters and an organisation-scoping requirement, the definition still leaves too much to the schema and gives no sense of which filters are most discriminating or how the lifecycle date filters interact.

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?

The description groups the filters into type, customer, status and per-lifecycle-step dates, which helps map to received_issued, customer_id, status and the date_*_from/to pairs. However, with most of the nested properties carrying no schema description, several parameters (year, number, reference, analytics_id, customer_id) get no meaning from either source.

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?

"List sales and purchase orders with filters for type, customer, status and the date of each life-cycle step" gives a specific verb (list) and resource (orders), and names the filterable dimensions, which distinguishes it from siblings like minimax_list_issued_invoices or minimax_list_received_invoices only implicitly — the reader must infer that this is the combined order stream.

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 never says when to pick this tool over the invoice-specific siblings (minimax_list_issued_invoices, minimax_list_received_invoices) even though it clearly overlaps with them. There is also no guidance on pagination behaviour, default organisation resolution, or prerequisites such as needing an organisation_id.

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