Skip to main content
Glama

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

Get cloned voice slots

minimax_get_voice_quota
Read-onlyIdempotent

How many cloned voice slots an account holds (total) and how many are in use (used), plus free clone previews left ("inf" when unlimited). Check it before minimax_clone_voice; minimax_delete_voice frees a slot. The count is advisory: MiniMax can let used exceed total, and the clone itself gives the final refusal. GET /speech/equity.

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

Input Schema

NameRequiredDescriptionDefault
accountNoThe MiniMax account id (minimax_list_accounts) to read. Required when you have several MiniMax accounts; with one it may be left out.

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?

Adds real context beyond the readOnly/idempotent annotations: the count is advisory, MiniMax can let used exceed total, and the clone call itself issues the final refusal. It also discloses the 'inf' sentinel for unlimited previews, which the agent cannot learn from annotations. Return shape is described in prose but field names/nesting are not stated, keeping it short of 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.

Conciseness5/5

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

Three tight sentences: what it returns first, then usage routing, then the advisory caveat. The trailing 'GET /speech/equity' is the only near-redundant element and is harmless.

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 carries the return-value burden and does so fully: total, used, and free previews with the 'inf' edge case called out. The advisory-vs-authoritative distinction is exactly the caveat an agent needs before gating a clone on this check.

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 account parameter already documents the multi-account requirement and points at minimax_list_accounts, so the description does not need to compensate. It adds no additional meaning about the parameter itself, which is the baseline for fully documented single-parameter schemas.

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 resource and exactly what it returns: total cloned voice slots, slots in use, and remaining free clone previews. Naming minimax_clone_voice and minimax_delete_voice makes it distinguishable from siblings without opening any schema.

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 timing guidance — 'Check it before minimax_clone_voice' — and explains the cause/effect relationship with minimax_delete_voice freeing a slot. The agent knows both when to call it and which operations it relates to.

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