Skip to main content
Glama
Minimax MCP Server

Minimax MCP Server

by chehcore

Run Minimax Record Action

minimax_run_action

Run business actions on accounting records, such as issuing invoices, confirming orders, approving inbox items, and generating PDFs, while handling accounting consequences.

Instructions

Run a business action on a record: issue an invoice, cancel issuing, generate its PDF, turn it into a credit note, send an e-invoice; confirm, complete or invoice an order; confirm a stock entry; approve or reject an inbox item.

Most actions have accounting consequences (issuing assigns the invoice number and posts it); state what you are about to do before running one.

Returns: str: JSON result from Minimax (for copy actions, the new record), or an "Error: ..." string.

Examples: - Issue draft invoice 4711 with PDF -> resource="issued_invoices", record_id=4711, action="issueAndGeneratepdf" - Turn order 88 into an invoice -> resource="orders", record_id=88, action="createissuedinvoice"

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

Input Schema

NameRequiredDescriptionDefault
paramsYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=false, openWorldHint=true, idempotentHint=false, so the mutation and open-world profile is known. The description adds genuinely new behavioral context beyond that: that most actions have accounting consequences and that issuing assigns the invoice number and posts it, plus that non-copy actions return a JSON status string. It does not address idempotency/retry behavior despite idempotentHint=false, which would have been valuable.

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

Conciseness5/5

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

Front-loaded with the action catalog, then the risk warning, then return shape, then two worked examples. Every section earns its place and there is no filler; the enumeration is long but it is the tool's actual surface area.

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 mutating, multi-resource action dispatcher this covers purpose, side effects, and return type adequately, and an output schema exists so return values need no elaboration. The small redundancy of restating the return shape and the absence of any retry/idempotency note are the only gaps.

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 schema already documents each property, and the description goes further by mapping business goals to concrete resource/action pairs through worked examples (invoice 4711 -> resource="issued_invoices", action="issueAndGeneratepdf"), which clarifies the otherwise non-obvious resource-action coupling. It does not add anything on parameters, row_version, or include_file_data beyond the schema.

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 ("Run a business action on a record") and then enumerates the exact resource/action combinations it covers (invoice issue/cancel/PDF/credit note/e-invoice, order confirm/complete/invoice, stock entry confirm, inbox approve/reject). This is clearly distinguishable from read/create/update/delete siblings, which operate on records rather than executing business state transitions.

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?

The description conveys the domain in which the tool applies (business actions with accounting consequences) and warns the agent to state intent before running one. However, it offers no when-not guidance and does not resolve overlap with siblings such as minimax_get_record_pdf versus the generatepdf action, or minimax_update_record versus the cancel/confirm actions. Usage is implied from the action catalog rather than explicitly routed.

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