Skip to main content
Glama
Minimax MCP Server

Minimax MCP Server

by chehcore

Get Minimax Dashboard

minimax_get_dashboard
Read-onlyIdempotent

Retrieve an organisation's financial dashboard with invoice summaries, unpaid invoices, top customers, debtors, creditors, and revenue versus expenses to answer how the company is doing.

Instructions

Return the organisation's dashboard: issued/received invoice summaries, unpaid invoices, top customers, debtors, suppliers and creditors, and revenue versus expenses. A good first call for "how is the company doing" questions.

Returns: str: JSON dashboard, 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_dashboard"
  }
}

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
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and openWorld, so safety is covered structurally. The description adds the error-return convention ('Error: ...' string) and the aggregate/rollup nature of the result, which is useful. It says nothing about organisation scoping or permissions, so it adds only modest context beyond the annotations.

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 short paragraphs, front-loaded with the payload contents, with the usage hint immediately after. The 'Returns:' block is somewhat boilerplate given an output schema exists, but it is short and still informative about the error string.

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?

For a single-parameter aggregate read with full annotations and an output schema, the agent has enough to call it correctly: what comes back, when it is the right first call, and how errors appear. Only organisation-defaulting behavior and permission requirements are left implicit.

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?

The OrgInput schema description already defines organisation_id (source tool, and that it may be omitted when a server default exists), so the schema covers the parameter even though coverage counts it at 0%.

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 (return) and resource (the organisation's dashboard), then enumerates the payload: invoice summaries, unpaid invoices, top customers, debtors/creditors, revenue vs expenses. That enumeration clearly distinguishes it from the list_* siblings, which return individual records. It stops short of naming any sibling as an alternative, so not a 5.

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?

'A good first call for "how is the company doing" questions' gives a concrete entry-point condition that steers the agent here before drilling into detail tools. It offers no explicit when-not-to-use or excluded case (e.g. single-invoice lookups go elsewhere), so it falls short of a 5.

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