Skip to main content
Glama
Minimax MCP Server

Minimax MCP Server

by chehcore

List Minimax Journal Entries

minimax_list_journal_entries
Read-onlyIdempotent

List individual general-ledger debit and credit postings across journals by account, customer, or date range to review balances, open items, and period activity.

Instructions

List individual general-ledger postings (debit/credit lines) across journals: the basis for account balances, open items of a customer, or what was booked to an account in a period.

Returns: str: JSON SearchResult with has_more.

Examples: - "What was booked to account 4100 in Q1?" -> account="4100", date_from="2026-01-01", date_to="2026-03-31"

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

Input Schema

NameRequiredDescriptionDefault
paramsYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4/5.0
Behavior4/5

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

The annotations already declare read-only, idempotent, non-destructive, and open-world behavior. The description adds useful behavioral context by stating the return is a JSON SearchResult with has_more, which indicates pagination, and the example demonstrates typical filtering behavior.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is front-loaded with a clear purpose sentence, followed by a compact return note and one targeted example. Every sentence earns its place and there is no redundant wording.

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?

Given the tool's complexity as a filtered listing endpoint, the description is reasonably complete: it explains the resource, return pagination indicator, and a representative query mapping. The output schema and annotations cover much of the remaining structure, though explicit routing against sibling journal tools is still missing.

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 schema contains many nested filter fields with some descriptions, but the description only clarifies account, date_from, and date_to via a concrete example. This example adds meaningful query-to-parameter mapping, but it leaves most filters such as status, journal_type, customer_id, and organisation_id without additional semantic guidance in the description.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb and resource: 'List individual general-ledger postings (debit/credit lines) across journals.' It also scopes the tool by explaining it is the basis for account balances, customer open items, and period bookings, which distinguishes it from journal-header listings such as minimax_list_journals.

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 description implies usage through examples like 'What was booked to account 4100 in Q1?' and by naming account balances and open items. However, it does not explicitly say when to use this tool versus sibling tools like minimax_list_journals or minimax_get_record, nor does it state exclusions.

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