Skip to main content
Glama
Minimax MCP Server

Minimax MCP Server

by chehcore

Delete Minimax Record

minimax_delete_record
DestructiveIdempotent

Permanently delete a record from Minimax accounting data. Prevents deletion when the record is used elsewhere, returning an error that explains why.

Instructions

Permanently delete a record. Minimax refuses to delete records already used elsewhere (a customer with invoices, an issued invoice); the error says why.

Returns: str: JSON {"ok": true} 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_delete_record"
  }
}

Input Schema

NameRequiredDescriptionDefault
paramsYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true, idempotentHint=true and readOnlyHint=false, so the safety profile is covered structurally. The description adds real value beyond that: permanence, the referential-integrity refusal rule, and the error-message behavior. It stops short of stating permission requirements or what happens to nested/child records.

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?

Two short, front-loaded sentences with no filler; the deletion constraint is stated before the return format. The "Returns: str: JSON {...}" block is slightly awkwardly formatted but not wasteful.

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?

An output schema exists, so the return-value note is redundant but harmless, and annotations cover the destructive/idempotent profile. What is missing for a destructive, 20-resource tool is any hint about the resource taxonomy or the parent_id requirement for nested resources, leaving the agent to read the schema to call it correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is reported at 0% for the top-level params object, so the description is expected to compensate, and it says nothing about resource, record_id, parent_id, or organisation_id. The nested schema does document these fields, but the description adds no meaning of its own about which resource values exist or when parent_id is required.

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?

States a specific verb and effect ("Permanently delete a record") and the schema's resource enum scopes it to Minimax entities. It is clearly distinguishable from create/get/update siblings by the verb, though the description itself never names the resource domain or a sibling.

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?

Provides one genuinely useful usage constraint: Minimax refuses to delete records referenced elsewhere (customer with invoices, issued invoice) and the error explains why. However, there is no guidance on when to delete versus update/archive, no mention of confirmation or irreversibility workflow, and no routing to alternatives.

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