Skip to main content
Glama

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

Get one account

minimax_get_account
Read-onlyIdempotent

One stored MiniMax account by id: host, maxJobs, supported features (supportVideo, supportAudio, supportMusic, supportAgent, supportChat), session issue and expiry times, and the stored account error if MiniMax put it on hold. No call to MiniMax; use minimax_get_features for live credits, minimax_list_accounts for all accounts. GET /accounts/{account}.

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": {
      "account": "<account>"
    },
    "name": "minimax_get_account"
  }
}

Input Schema

NameRequiredDescriptionDefault
accountYesThe account id as minimax_list_accounts shows it.

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A4.5/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 safe read, so the description's added value is the disclosure that data is locally stored rather than fetched live, plus the fact that a held/paused account surfaces as a stored error. There is mild tension between 'No call to MiniMax' and openWorldHint=true, since the tool itself touches no external system, but the safety profile is not contradicted.

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?

A single dense sentence plus a routing sentence and the endpoint; the returned fields are front-loaded and nothing is repetitive or wasted.

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

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema, the description compensates by enumerating the return fields, and it explains the local-vs-live data distinction and the account-id source. For a one-parameter read tool this is sufficient to invoke 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?

Only one parameter, already documented at 100% schema coverage ('The account id as minimax_list_accounts shows it'). The description's 'by id' adds no format, sourcing, or validation 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 resource ('One stored MiniMax account by id') and enumerates the returned fields (host, maxJobs, feature flags, session issue/expiry, stored error). It names the sibling tools it is not (minimax_get_features, minimax_list_accounts), so an agent can distinguish it 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?

Explicitly scopes usage: read of a single stored account, 'No call to MiniMax', and directs the agent to minimax_get_features for live credits and minimax_list_accounts for the full list. This is a direct when-to-use/when-not/alternative routing statement.

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