Skip to main content
Glama
Minimax MCP Server

Minimax MCP Server

by chehcore

List Minimax Stock Entries

minimax_list_stock_entries
Read-onlyIdempotent

List stock entries including goods receipts, issues, own use, and transfers; filter by date, status, type, subtype, organisation, or page and return JSON results with has_more.

Instructions

List stock entries (goods receipts, issues, own use, transfers).

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

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=true, idempotentHint=true, destructiveHint=false, and openWorldHint=true, so the safety profile is covered. The description adds useful domain context about what stock entries include and mentions has_more, but it does not disclose pagination behavior, default-organisation handling, or other operational constraints.

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?

The description is short and front-loaded with the core purpose. The return-value sentence is mildly redundant because an output schema exists, but it does not materially bloat the definition.

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?

For a list tool with numerous nested filter parameters, the description is thin: it gives no guidance on filtering, pagination, or default organisation behavior. However, annotations cover safety traits and the output schema covers return structure, so the remaining gap is moderate rather than severe.

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 names entry categories that loosely correspond to stock_entry_type and subtype values, but it adds no real explanation of the many filters such as date_from, date_to, status, sort_field, or organisation_id. The nested schema does document most of those fields, so the schema carries most of the parameter meaning.

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 entries,' with parenthetical examples of entry categories. This is clear enough to identify the operation, but it does not explicitly distinguish it from nearby siblings such as minimax_list_stock or minimax_list_journal_entries.

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 explicit when-to-use guidance, no exclusion criteria, and no named alternatives. The agent must infer that this tool is for listing stock entries rather than using another inventory-related list tool.

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