Skip to main content
Glama
Minimax MCP Server

Minimax MCP Server

by chehcore

Update Minimax Record

minimax_update_record
Idempotent

Updates selected fields of an existing accounting record by applying only the provided changes and preserving the current row version; supports customers, invoices, items, and journals.

Instructions

Change fields of an existing record. Reads the current record, applies changes on top, and writes it back with the current RowVersion, so only the fields named in changes are affected.

Issued (non-draft) invoices cannot be edited; cancel issuing first with minimax_run_action.

Returns: str: JSON of the updated record, or an "Error: ..." string.

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

Input Schema

NameRequiredDescriptionDefault
paramsYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.1/5.0
Behavior5/5

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

Beyond the annotations it discloses the read-modify-write mechanism, that only fields named in `changes` are mutated, and that the write is guarded by the current RowVersion. This is consistent with idempotentHint=true and destructiveHint=false and explains why the tool is safe to retry.

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?

Three short blocks front-loading the mutation semantics, then the blocking precondition, then the return type. The backtick-quoted field names and embedded 'Returns:' line are slightly noisy but each sentence carries information.

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 mutation tool with an output schema and partial-update semantics, the description covers the mechanism, the concurrency guard, and the main failure mode. Missing only peripheral detail such as permission requirements or how the resource enum scopes the operation.

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?

With zero top-level schema description coverage, the description must carry parameter meaning, and it explains `changes` (only named fields affected, whole-field replacement implied by the schema) and the RowVersion conflict rule. It says nothing about `resource`, `parent_id`, `record_id`, or `organisation_id`, so compensation is partial.

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?

"Change fields of an existing record" gives a specific verb and resource, and the read-modify-write explanation makes the operation's nature unmistakable against minimax_create_record and minimax_get_record. It stops short of naming those siblings explicitly, but the scope is unambiguous.

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?

It states a concrete exclusion (issued, non-draft invoices cannot be edited) and routes the agent to the named alternative, minimax_run_action, to cancel issuing first. It does not address the general update-vs-create choice, but the one genuinely blocking precondition is covered.

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