Skip to main content
Glama
Minimax MCP Server

Minimax MCP Server

by chehcore

Create Minimax Record

minimax_create_record

Creates records such as customers, items, invoices, orders, and journal entries, validates fields against the Minimax schema, and returns new IDs; invoices and orders start as drafts.

Instructions

Create a record (customer, item, issued invoice, order, journal, ...).

New invoices, orders and stock entries are created as drafts; issue or confirm them afterwards with minimax_run_action. Field names are checked against the Minimax schema before anything is sent.

Returns: str: JSON of the created record (with its new ID and RowVersion), or an "Error: ..." string.

Examples: - New customer -> resource="customers", data={"Name": "Novak d.o.o.", "Address": "Slovenska 1", "PostalCode": "1000", "City": "Ljubljana", "Country": {"ID": }}

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

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
Behavior4/5

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

Annotations already declare the safety profile (readOnlyHint=false, destructiveHint=false, idempotentHint=false), so the bar is lower, yet the description adds genuinely non-obvious behavior: created invoices/orders/stock entries are drafts that require a follow-up minimax_run_action, and field names are validated against the schema before anything is sent. It does not discuss permission requirements, org defaults, or rate/error conditions beyond the returned "Error: ..." string, so it is strong but not exhaustive.

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?

It is well front-loaded: the core action, then the draft/run_action caveat, then return shape, then an example. The example is somewhat long and ends with an inline placeholder expression ("<id from minimax_get_record ...>") that is harder to parse than the prose around it, but nothing is padding.

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 create tool with a full output schema, the description covers what an agent most needs: what is created, that drafts need a second action, that fields are validated, and what comes back. The one gap is that it does not state prerequisites such as consulting minimax_describe_resource for field names (that hint lives only in the schema) or resolving organisation_id via minimax_list_organisations.

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?

The schema itself documents resource, data, parent_id and organisation_id, and the description's only parameter-level contribution is the worked example showing resource="customers" with a data payload and a {"ID": <id>} reference. It adds a useful concrete usage pattern but no additional semantics for parent_id or organisation_id, so it sits at the adequate baseline.

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 and resource ("Create a record") and enumerates concrete record types (customer, item, issued invoice, order, journal), which is enough for an agent to distinguish it from read/update/delete siblings by name alone. It does not explicitly name minimax_update_record as the alternative for modifying existing records, so it stops short of a 5.

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 gives real routing guidance: new invoices, orders and stock entries land as drafts and must be issued/confirmed via minimax_run_action, and the example shows that reference IDs come from minimax_get_record (e.g. countries by code). That covers the main when-to-use and next-step cases, but there is no explicit statement of when NOT to use this tool (e.g. for existing records, use minimax_update_record).

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