Skip to main content
Glama
Minimax MCP Server

Minimax MCP Server

by chehcore

Get Minimax Record

minimax_get_record
Read-onlyIdempotent

Fetch a complete accounting record by ID, code, content, or date, including its RowVersion and nested rows such as invoice lines or journal entries. Useful for retrieving full Minimax resource details.

Instructions

Fetch one complete record, including its RowVersion and nested rows (invoice rows, journal entries, ...).

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

Examples: - Issued invoice 4711 -> resource="issued_invoices", key="4711" - Item with code "SKU-1" -> resource="items", key="SKU-1", by="code"

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

Input Schema

NameRequiredDescriptionDefault
paramsYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/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 covered structurally. The description adds genuinely new behavioral context beyond those annotations: the return is a JSON string, includes RowVersion and nested rows, and failures surface as an 'Error: ...' string. It says nothing about not-found behavior, permission scoping, or size when include_file_data is set, so a 3 is appropriate.

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?

The definition is short and front-loaded: the fetch semantics come first, then the return contract, then two compact examples. The 'Returns: str: JSON record...' line is somewhat redundant given an output schema exists, but it is one line and sets expectations for the error case, so little is wasted.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With rich annotations and an output schema present, the description need not explain return values or safety, and it correctly focuses on the record-fetch contract and lookup examples. However, for a 29-resource dispatcher with nested-resource handling (parent_id required for customer_*, document_attachments, journal_vat_entries), the description gives no guidance on those structural cases or on resolving organisation_id, leaving meaningful gaps.

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 reported schema coverage is 0% (the top-level 'params' wrapper carries no description), and the description compensates only partially by demonstrating the resource/key/by combination for two resources. It adds real value by showing by="code" in practice, but it never mentions parent_id, organisation_id, include_file_data, or the date/content lookup modes, leaving several parameters to the nested schema alone.

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: 'Fetch one complete record', and immediately scopes the result as including RowVersion and nested rows (invoice rows, journal entries). That distinguishes it from the list_* siblings, which return collections rather than a single hydrated record. It does not explicitly name a sibling tool, 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 Guidelines3/5

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

The two worked examples ('Issued invoice 4711' -> resource/key, 'Item with code SKU-1' -> by="code") implicitly convey when to use the tool and how lookup modes apply. There is no explicit statement of when NOT to use it (e.g., prefer list_issued_invoices for multiple records) and no mention of prerequisites such as resolving an organisation_id or consulting minimax_describe_resource first.

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