Skip to main content
Glama
Minimax MCP Server

Minimax MCP Server

by chehcore

List Minimax Issued Invoices

minimax_list_issued_invoices
Read-onlyIdempotent

Retrieve issued invoices or proforma invoices with filters for customer, dates, status, and payment status to track receivables and overdue payments.

Instructions

List issued invoices (or proforma invoices) with filters for customer, dates, status and payment status.

Returns: str: JSON {Rows: [{IssuedInvoiceId, InvoiceNumber, Customer, DateIssued, DateDue, Status, PaymentStatus, InvoiceValue, PaidValue, ...}], TotalRows, CurrentPageNumber, PageSize, has_more}.

Examples: - "Unpaid overdue invoices" -> payment_status="NeplacanZapadel" - "Invoices to Novak in March 2026" -> customer_name="Novak", date_issued_from="2026-03-01", date_issued_to="2026-03-31"

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

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, destructiveHint=false and idempotentHint=true, so the safety profile is fully covered. The description adds nothing beyond the annotations on pagination behavior, default organisation handling, or result-count limits — page/page_size exist only in the schema. Adequate but not additive.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The one-line purpose is well front-loaded and the examples are compact and useful. However, the multi-line 'Returns' block restates the row shape that the output schema already defines, which is wasted space under the stated rule that a description needn't explain return values when an output schema exists.

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?

Given a rich nested input schema, full annotations, and a published output schema, the description covers the essential gap: how filters combine in practice. The remaining omissions — sibling differentiation and guidance that organisation_id may be omitted — are minor, with the latter already noted in the schema.

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?

The examples translate user intent into concrete parameter combinations, e.g. 'overdue unpaid' -> payment_status='NeplacanZapadel' and a month range -> customer_name plus date_issued_from/date_issued_to. Most of the 21 nested fields (organisation_id, payment_status, status, invoice_type, page_size) already carry schema descriptions, so the description's contribution is the worked combinations rather than field-level definitions.

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 opens with a specific verb+resource ('List issued invoices (or proforma invoices)') and enumerates the filter dimensions, so the agent knows exactly what the tool returns. It implicitly separates itself from minimax_list_received_invoices via the 'issued' qualifier, but never names an alternative explicitly.

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 through two example requests ('Unpaid overdue invoices', 'Invoices to Novak in March 2026'), which show how to drive the filters but not when this tool is preferred over siblings such as minimax_list_received_invoices or minimax_list_issued_invoice_postings. No exclusions or prerequisites are stated.

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