Skip to main content
Glama
Minimax MCP Server

Minimax MCP Server

by chehcore

Get Minimax Item Settings

minimax_get_items_settings
Read-onlyIdempotent

Retrieve an organisation's item settings—price decimals, stock valuation, and item-code generation—before creating items to ensure new records match configured accounting rules.

Instructions

Return the organisation's item settings (price decimals, stock valuation, whether item codes are generated), useful before creating items.

Returns: str: JSON settings, 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_get_items_settings"
  }
}

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, openWorldHint and destructiveHint=false, so the safety profile is fully covered elsewhere. The description's only added behavioral detail is the error convention (an 'Error: ...' string instead of JSON), which is useful but thin. It says nothing about default-organisation fallback behavior or the cost of an open-world call.

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 blocks: purpose plus scope first, then a Returns note. Every sentence carries information, though the Returns line partially duplicates the existing output schema.

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?

The description is adequate for a simple read tool: annotations cover safety, an output schema exists so return shape needn't be restated, and the use case is stated. The gap is the sole parameter, which is left entirely unexplained despite being required and scoped by organisation.

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?

The tool takes one required parameter (the nested organisation_id), and the description never mentions it — no explanation of what identifying an organisation changes or what happens when it is omitted. With reported schema description coverage at 0%, the description is expected to compensate and does not.

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 states a specific verb and resource ('Return the organisation's item settings') and enumerates the settings covered (price decimals, stock valuation, item-code generation), which separates it from data-oriented siblings like minimax_get_items_data. It does not name a sibling explicitly, 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 Guidelines4/5

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

'Useful before creating items' gives a concrete precondition for calling this tool, which is real when-to-use guidance rather than an implied purpose. There is no statement of when not to use it and no named alternative for related settings lookups, so it is clear but not exhaustive.

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