Skip to main content
Glama
Minimax MCP Server

Minimax MCP Server

by chehcore

Create Minimax Customer From Tax Number

minimax_create_customer_by_tax_number

Create a customer from a tax number alone; the business register fills in name and address automatically, reducing manual entry errors for domestic companies.

Instructions

Create a customer by tax number alone: Minimax fills name and address from the national business register. Faster and less error-prone than minimax_create_record for domestic companies.

Returns: str: JSON of the created customer, 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_create_customer_by_tax_number"
  }
}

Input Schema

NameRequiredDescriptionDefault
paramsYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare this is a non-read-only, open-world, non-idempotent, non-destructive operation, so the safety profile is covered. The description adds real value by disclosing the external data source (national business register) and the error convention ("Error: ..." string instead of a structured failure). It does not address what happens on repeat calls for the same tax number, or what happens when the register lookup finds nothing.

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 core value proposition is front-loaded in the first clause, followed by the sibling comparison. The trailing "Returns:" block is largely redundant since an output schema exists and duplicates the JSON/error-string contract, which is the only wording that fails to earn its place.

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?

For a single-required-parameter creation tool with annotations and an output schema, the definition covers purpose, data source, and error signalling. The notable gap is duplicate/creation semantics for a non-idempotent create: an agent cannot tell from the description whether calling twice with the same tax number produces a second customer or an error.

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 input schema itself documents both tax_number (format example) and organisation_id (default, lookup via minimax_list_organisations), so the parameter meaning is largely carried by the schema regardless of the reported 0% coverage metric. The description contributes only the constraint that tax_number is sufficient on its own; it says nothing about organisation_id or when to supply it.

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?

The description states a specific verb and resource (create a customer) plus the defining mechanism: the tax number alone, with name and address auto-filled from the national business register. It explicitly distinguishes itself from the sibling minimax_create_record, so an agent can choose between the two without opening either schema.

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?

"Faster and less error-prone than minimax_create_record for domestic companies" gives a clear selection rule and names the alternative. The qualifier "for domestic companies" implicitly bounds applicability, but the description never states the negative case (e.g. foreign entities or customers whose register data is missing), so the exclusion is left to inference.

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