Skip to main content
Glama
Minimax MCP Server

Minimax MCP Server

by chehcore

List Minimax Received Invoices

minimax_list_received_invoices
Read-onlyIdempotent

List received supplier invoices and filter them by supplier, issue/due dates, status, and payment status to review payables.

Instructions

List received (supplier) invoices with filters for supplier, dates, status and payment status. Unprocessed incoming e-invoices are in the inbox instead (minimax_list_inbox).

Returns: str: JSON {Rows: [{ReceivedInvoiceId, DocumentReference, Customer, DateIssued, DateDue, Status, PaymentStatus, InvoiceAmount, ...}], ...}.

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

Input Schema

NameRequiredDescriptionDefault
paramsYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so the safety profile is fully covered without description help. The description adds a return shape (row keys such as ReceivedInvoiceId, Status, PaymentStatus), but says nothing about pagination behavior, default page size, or the organisation-scoping requirement that a listing tool would need.

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?

Front-loaded with the core action and filters, then the inbox exclusion, then a returns block. Roughly four lines with little waste, though the returns block duplicates information an output schema already supplies.

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 read-only, paginated list tool with a real output schema and strong annotations, the description covers purpose, routing and return shape. Remaining gaps (page/page_size defaults of 50 and max 1000, organisation_id fallback) are documented in the schema, so nothing essential is missing from the definition as a whole.

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?

Reported schema description coverage is 0%, so the description carries part of the burden; it summarizes the filter families (supplier, dates, status, payment status), which maps loosely onto customer_id/customer_name, date_* and status/payment_status. It adds no syntax or format detail (date format, enum meaning, payment_status values) — that detail lives in the schema properties rather than here, so this is adequate but not compensating for the measured gap.

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?

States a specific verb and resource ('List received (supplier) invoices') plus the filterable dimensions, which immediately separates it from minimax_list_issued_invoices. It also names the sibling it is not (minimax_list_inbox) for unprocessed e-invoices, so an agent can pick between the two without opening a schema.

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

Usage Guidelines4/5

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

Gives one explicit routing rule: unprocessed incoming e-invoices belong in minimax_list_inbox instead. That is genuine when-not guidance, but coverage of the wider sibling set is thin — nothing explains how this relates to issued invoices or posting/journal listing tools beyond the self-evident name.

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