Skip to main content
Glama
Minimax MCP Server

Minimax MCP Server

by chehcore

Get Minimax Item Stock

minimax_get_item_stock
Read-onlyIdempotent

Fetch item stock across warehouses or for a single warehouse, optionally by date, batch, or organisation. Returns JSON stock records or an error message.

Instructions

Return the stock of one item, across warehouses or in one.

Returns: str: JSON stock record(s), 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_item_stock"
  }
}

Input Schema

NameRequiredDescriptionDefault
paramsYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so the safety profile is covered. The description adds only that errors come back as an 'Error: ...' string, which is mildly useful for parsing but thin relative to an open-world external system 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?

A single front-loaded sentence with no padding. The 'Returns:' stanza is arguably redundant because an output schema exists, but it is short enough not to hurt readability.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a tool with five parameters, an open-world external backend, and no schema descriptions on most fields, the description answers almost nothing an agent needs beyond the one-line purpose. Return-value documentation is unnecessary given the output schema, and no guidance routes the agent between this and the stock listing siblings.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Reported schema description coverage is 0%, so the description carries the burden; 'across warehouses or in one' is the only hint about warehouse_id, and it never mentions item_id, batch_number, or as_of. Parameters like batch_number are left completely unexplained.

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 (return the stock of one item) plus a scope variation (across warehouses or in one). It does not distinguish itself from sibling list tools such as minimax_list_stock or minimax_list_stock_entries, leaving the agent to infer the single-item vs listing difference.

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 'one item' implies this is the per-item lookup rather than a bulk listing, but the description never states when to prefer it over minimax_list_stock or what prerequisites apply. Usage is only inferable, not stated.

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