Skip to main content
Glama
Minimax MCP Server

Minimax MCP Server

by chehcore

List Minimax Outbox

minimax_list_outbox
Read-onlyIdempotent

Retrieve and paginate documents Minimax has sent electronically, including issued invoices, delivery notes, and payslips, with date, type, and organisation filters.

Instructions

List the outbox: documents Minimax has sent electronically (issued invoices, delivery notes, payslips).

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_outbox"
  }
}

Input Schema

NameRequiredDescriptionDefault
paramsYes

Output Schema

NameRequiredDescriptionDefault
resultYes

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 readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=true, so safety and idempotency are covered and the description is not required to restate them. The description adds a small amount of value by disclosing that the result is a JSON SearchResult carrying has_more, which hints at pagination. It says nothing further about ordering defaults, page-size caps, or the fact that an unconfigured organisation causes failure.

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 sentences, front-loaded with the purpose before the return note, with no padding. The 'Returns: str: JSON SearchResult with has_more' line is slightly awkward and duplicates ground already covered by the output schema, but it is brief enough not to be wasteful.

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?

For a simple read-only list tool with a rich nested input schema and an output schema, the description supplies the essential framing: what subset of documents is listed and the shape of the paged result. It could be stronger by naming the inbox sibling and by flagging the organisation_id requirement, but nothing an agent needs to invoke the tool correctly is materially 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?

The description itself adds no parameter meaning at all; the input schema does most of the work, documenting page, order, page_size, sort_field, outbox_type and organisation_id. Gaps remain for date_from, date_to and import_status, which are undocumented in both schema and description, so the description neither compensates for those gaps nor repeats what the schema already covers.

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 names a specific verb and resource ('List the outbox') and defines scope precisely as documents Minimax has sent electronically, enumerating the three document types (issued invoices, delivery notes, payslips). That 'has sent' framing implicitly separates it from minimax_list_inbox, but it never names that sibling explicitly, so the differentiation is inferential rather than stated.

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?

Usage is implied by the scope definition: an agent can reason that this is the tool for outbound/issued documents. However, there is no explicit when-to-use versus minimax_list_inbox, minimax_list_issued_invoices, or minimax_list_issued_invoice_postings, and no guidance on prerequisites such as needing an organisation_id or a configured default organisation.

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