Skip to main content
Glama
Minimax MCP Server

Minimax MCP Server

by chehcore

List Minimax Stock

minimax_list_stock
Read-onlyIdempotent

List stock quantities and values by item and warehouse, with optional filters for a past date or batch number, to review inventory levels and valuation.

Instructions

List stock quantities and values per item and warehouse, optionally as of a past date or by batch number.

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

Input Schema

NameRequiredDescriptionDefault
paramsYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/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 covered. The description adds the return shape ('JSON SearchResult with has_more'), which usefully signals pagination, but says nothing about permissions, defaults, or result size limits.

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 tight sentences with the core purpose front-loaded, followed by a brief return note. No filler, though the 'Returns:' block is somewhat redundant given an output schema exists.

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?

Adequate for a read-only list tool with a rich nested schema and an output schema. It omits guidance on the organisation_id default and on how pagination should be driven, which an agent would need for correct repeated calls.

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 maps loosely onto key parameters (as_of, by_batch_number, item/warehouse scoping), adding some meaning. However, the nested schema already documents most fields in detail, so the description contributes little beyond what structured data provides.

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 stock quantities and values') plus scope ('per item and warehouse'), which is clear. It does not differentiate from close siblings such as minimax_get_item_stock or minimax_list_stock_entries, so an agent cannot tell from the description alone which one to pick.

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?

The phrase 'optionally as of a past date or by batch number' hints at parameter usage but gives no when-to-use or when-not-to-use guidance. No alternative tool is named and no prerequisites (e.g. organisation context) are stated.

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