Skip to main content
Glama
Minimax MCP Server

Minimax MCP Server

by chehcore

List Minimax Journals

minimax_list_journals
Read-onlyIdempotent

List general-ledger journals with filters for type, status, date range and description. Retrieve paginated results to find a journal, then fetch its entries separately for full details.

Instructions

List general-ledger journals (temeljnice) with filters for type, status and date. Use minimax_get_record (resource="journals") for a journal's entries.

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

Input Schema

NameRequiredDescriptionDefault
paramsYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and open-world behavior, so the safety profile is covered. The description adds genuinely new context by stating the return is a JSON SearchResult carrying has_more, which signals pagination — information an agent would otherwise have to infer.

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?

Front-loaded with the purpose in the first clause, followed by the sibling routing hint and a short return note. The 'Returns: str:' phrasing is a mild Python-typing leftover but costs little space and adds a useful has_more signal.

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

Completeness4/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-value note is bonus rather than necessity, and the schema documents the individual parameters and the default-organisation behavior. The only real gap is the unmentioned minimax_list_journal_entries sibling, which an agent might confuse with this list tool.

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 only summarizes filter families ('type, status and date'), mapping loosely to journal_type, status and date_from/date_to, and says nothing about paging, sorting, description matching, from_journal_id or organisation_id. The input schema does carry per-field descriptions for most of these, so the description neither compensates nor conflicts, landing at baseline.

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 general-ledger journals (temeljnice)') and names the filter dimensions it supports. It also carves itself apart from minimax_get_record by scope, though it does not address the closely named minimax_list_journal_entries sibling.

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?

Gives an explicit routing rule: use this tool for the journal list, and use minimax_get_record with resource="journals" for a single journal's entries. There are no explicit when-not conditions or other exclusions, but the primary ambiguity is resolved.

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