Skip to main content
Glama
Minimax MCP Server

Minimax MCP Server

by chehcore

List Minimax VAT Rates

minimax_list_vat_rates
Read-onlyIdempotent

Retrieve VAT rates valid on a given date, including another EU country's rates for OSS; use returned VatRateId values in invoice rows.

Instructions

List VAT rates valid on a date. Invoice rows reference a rate as {"VatRate": {"ID": }}.

Returns: str: JSON {Rows: [{VatRateId, Code, Name, Percent, ...}], ...}.

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

Input Schema

NameRequiredDescriptionDefault
paramsYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so the safety profile needs no restating. The description adds the downstream relationship between a VatRateId and invoice rows, which goes beyond the annotations, but says nothing about defaults in effect, permissions, or any rate/volume constraints.

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 purpose is front-loaded in the first sentence and the second sentence adds concrete linkage value. The trailing "Returns:" block largely duplicates the output schema, which is wasted space given has_output_schema is true, but the definition is otherwise tight.

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 simple, read-only, single-parameter list tool with full annotations and an output schema, the description covers purpose, date scoping and the VatRateId linkage sufficiently. The only real gap is sibling differentiation against minimax_list_vat_accounting_types.

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 description contributes nothing about as_of, country_id or organisation_id; all three are documented in the nested ListVatRatesInput schema (including defaults of today and home country), so the 0% top-level coverage is misleading and the fields are in fact explained. With no parameter meaning added beyond the schema, baseline 3 applies.

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 gives a specific verb and resource ("List VAT rates") plus a validity qualifier ("valid on a date"), so an agent knows exactly what is returned. It never distinguishes this from the close sibling minimax_list_vat_accounting_types, which is the main thing keeping it below 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?

Usage is only implied: the note that invoice rows reference a rate as {"VatRate": {"ID": <VatRateId>}} hints that this tool supplies IDs needed elsewhere, which is genuinely useful routing signal. There is no explicit when-to-use/when-not statement, no mention of the date-scoping or OSS country selection as selection criteria, and no reference to the vat_accounting_types alternative.

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