Skip to main content
Glama
Minimax MCP Server

Minimax MCP Server

by chehcore

Get Minimax Item Sales Data

minimax_get_items_data
Read-onlyIdempotent

Retrieves item data—price, discount, VAT rate, and stock—for a given customer and warehouse to populate accounting documents. Returns JSON or an error string.

Instructions

Return items with the data needed to put them on a document for a given customer and warehouse: price, discount, VAT rate, stock.

Returns: str: JSON list of item data, 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_data"
  }
}

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
Behavior4/5

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

Annotations already cover the safety profile (readOnlyHint, idempotentHint, destructiveHint=false, openWorldHint), so the bar is lower. The description adds real value by disclosing that failures are returned as an "Error: ..." string rather than raised, and by enumerating exactly which pricing fields come back per item.

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 the data payload stated before the return-type note. The "Returns: str:" docstring fragment is slightly redundant given an output schema exists, but nothing else is wasted.

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 explanation is a bonus rather than a necessity. However, for a tool whose inputs are four nullable IDs at 0% schema coverage, the description leaves key call-shaping questions unanswered — notably what happens when item_id, customer_id, or warehouse_id are omitted, and what conditions trigger the error string.

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 0% and all four nested fields (item_id, customer_id, warehouse_id, organisation_id) are nullable with defaults, so the description must carry the semantics. It only maps customer and warehouse; it never explains what item_id does (whether null yields all items or a literal lookup) or how organisation scoping interacts, leaving the most ambiguous parameter undocumented.

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?

Uses a specific verb and resource ("Return items with the data needed to put them on a document") and enumerates the payload fields: price, discount, VAT rate, stock. This clearly separates it from sibling readers such as minimax_get_item_stock or minimax_get_item_settings, though it never names an alternative explicitly.

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?

The phrase "data needed to put them on a document for a given customer and warehouse" implies the use case (document/quote/invoice line pricing), but there is no explicit when-to-use or when-not-to-use guidance relative to minimax_get_item_price_lists or minimax_get_item_stock, which overlap in territory.

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