Skip to main content
Glama

MiniMax MCP Server by useapi.net (third-party)

Get credits and plan

minimax_get_features
Read-onlyIdempotent

Ask MiniMax live for one account's video/image credits (totalCredits), plan (memberName, isPaidSubscription) and per-model settings (modelControl, as MiniMax reports them), plus the minimax.io audio credits for music and speech (audio.total_credit). Use before a generation to check credits, or after a 412; minimax_get_account shows stored settings without calling MiniMax. GET /features.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "minimax_get_features"
  }
}

Input Schema

NameRequiredDescriptionDefault
accountNoThe account id from minimax_list_accounts. Optional when you have one account, required with more.

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already cover read-only, idempotent, non-destructive, and open-world behavior, so the bar is lower. The description still adds real context: it makes a live remote call to MiniMax, names the endpoint (GET /features), discloses the returned field names in the absence of an output schema, and signals the 412 failure mode. It stops short of auth requirements or rate-limit behavior, so not a 5.

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?

Purpose and returned fields are front-loaded in the first clause, with usage guidance following, and nothing is redundant. The first sentence is dense with parenthetical field names, which is efficient but slightly harder to scan than a cleaner breakdown.

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?

With no output schema, enumerating the returned fields was essential and is done well, and the 412 reference plus the sibling contrast round out the model. Minor gaps remain around error handling beyond 412 and any call cost, but an agent has what it needs to invoke this correctly.

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?

Schema coverage is 100% and the single 'account' parameter is fully documented in the schema, including the optional-when-one-account rule. The description only implies account scoping via 'one account's' and adds no syntax or format detail beyond the schema, so the baseline 3 applies.

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?

States a specific verb and clearly enumerated resources: 'Ask MiniMax live for one account's video/image credits (totalCredits), plan (memberName, isPaidSubscription) and per-model settings... plus the minimax.io audio credits'. It also names the exact sibling it is not ('minimax_get_account shows stored settings without calling MiniMax'), so an agent can distinguish the two without opening schemas.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives explicit when-to-use triggers: 'before a generation to check credits, or after a 412', and pairs that with the alternative ('minimax_get_account shows stored settings without calling MiniMax'). Both the positive case and the routing decision are stated.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources