Skip to main content
Glama
Minimax MCP Server

Minimax MCP Server

by chehcore

List Minimax Inbox

minimax_list_inbox
Read-onlyIdempotent

Lists incoming e-invoices, bank statements, and other unprocessed documents from the inbox, with pagination and filters for type, date, status, and organisation.

Instructions

List the inbox: incoming e-invoices, bank statements and other documents waiting to be processed. Approve or reject with minimax_run_action.

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

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=true, idempotentHint=true, destructiveHint=false and openWorldHint=true, so safety and idempotency are covered structurally. The description adds that results are pending-processing documents and that the payload is a SearchResult carrying has_more, which hints at pagination, but says nothing about page-size limits, sort defaults, or what happens when organisation_id is omitted beyond what the schema notes.

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 plus a return line; the purpose statement is front-loaded and nothing is padded. The "Returns: str: JSON SearchResult with has_more" block is slightly wasteful given an output schema exists, but it is not enough to be a structural flaw.

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?

With an output schema present and rich annotations, the description need not explain return values or safety. It is still incomplete for a filtered, paginated listing tool: it omits the date-range and import-status filters, the meaning of the inbox types, and the default-organisation fallback, all of which an agent would want before calling it.

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 description mentions no parameters at all, leaving the agent entirely dependent on the nested schema. Reported coverage is 0% at the top level, and inside the nested object date_from, date_to and import_status carry no descriptions anywhere, so the description fails to compensate for real gaps around date filtering and import-status semantics.

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 gives a specific verb and resource ("List the inbox") and enumerates what the inbox contains: incoming e-invoices, bank statements, and other documents awaiting processing. That scope statement is genuinely informative, but it never distinguishes this tool from close siblings such as minimax_list_received_invoices or minimax_list_outbox, so the agent must infer the boundary.

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 only implied via "waiting to be processed" and the follow-up pointer "Approve or reject with minimax_run_action." That next-step hint is useful, but there is no explicit statement of when to use this versus the received-invoices or outbox listers, and no guidance on whether filtering is required for large inboxes.

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