Skip to main content
Glama
Minimax MCP Server

Minimax MCP Server

by chehcore

List Minimax Postal Codes

minimax_list_postal_codes
Read-onlyIdempotent

Lists postal codes for a specified country, with paging, search, and sorting options to retrieve matching codes or place names.

Instructions

List the postal codes of one country.

Returns: str: JSON SearchResult with has_more.

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

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 readOnly, idempotent, openWorld and non-destructive, so safety is covered. The description adds one genuine behavioral fact beyond that — results are paginated with a has_more flag — but says nothing about ordering defaults, result size limits, or auth/organisation scoping requirements.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two short blocks with the core action front-loaded and no filler. The Returns block is brief and arguably redundant with the output schema, but it costs almost nothing and is not padded.

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 paginated read with rich annotations, a fully described input schema and an output schema, the description plus structured fields are close to sufficient. The main residual gap is that an agent gets no hint about how to obtain country_id or when the organisation scope can be omitted — although the schema does mention both.

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 0% schema coverage understates what is visible: every property in ListPostalCodesInput (page, order, page_size, country_id, sort_field, search_string, organisation_id) carries its own inline description, so the schema does the heavy lifting. The description adds no meaning beyond it — for example, it never explains that search_string matches postal code or place name, or how country_id is obtained.

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 resource ('List the postal codes') plus a scope qualifier ('of one country'), which is enough for an agent to distinguish it from the other list_* siblings on different resources. It stops short of naming any sibling or contrasting behavior, so it lands at 4 rather than 5.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

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

There is no when-to-use guidance, no mention of alternatives (e.g. using get_record for a single lookup), and no note on when organisation_id must be supplied. The only implied constraint is the single-country scope, which the agent must infer from the sentence.

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