Skip to main content
Glama

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

Get speech settings

minimax_get_speech_config
Read-onlyIdempotent

The vocabularies speech accepts on an account: emotion values (t2a_emotion, for emotion in minimax_create_speech), and the voice tags by language, gender, age and accent (tag_name values for tag_list in minimax_list_voices; the language names also serve as language_boost and as language_tag in minimax_clone_voice). Read it before choosing those inputs. GET /speech/config.

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

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.4/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and open-world, so safety is covered. The description adds genuinely new behavioral context: the vocabulary is scoped per account and is a static reference set rather than generated content, and it discloses the underlying endpoint GET /speech/config. It stops short of describing return shape or caching/cost characteristics, but the account-scoping point is the practically important detail.

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?

Purpose and return content are front-loaded in the first clause, the action directive follows, and the endpoint is parked at the end. The parentheticals are dense but every one carries mapping information an agent needs, with no filler sentences.

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?

No output schema exists, so the description carries the burden of describing return content, which it does by enumerating the vocabularies and their dimensions. What is slightly under-specified is the shape of each vocabulary (e.g. whether tags are returned as name/value pairs grouped by language), which would remove the last guesswork before calling.

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 optional parameter, and schema coverage is 100% with a description explaining the multi-account conditioning rule. The description adds only the implicit 'on an account' scoping, so the schema does the real work; 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 resource ('the vocabularies speech accepts on an account') and enumerates exactly what it returns: emotion values and voice tags by language, gender, age and accent. It also names the specific downstream inputs each vocabulary feeds (t2a_emotion, tag_list, language_boost, language_tag), which distinguishes it clearly from sibling getters like minimax_get_speech or minimax_list_voices.

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 instructs 'Read it before choosing those inputs' and identifies the three tools whose inputs the values resolve (minimax_create_speech, minimax_list_voices, minimax_clone_voice). That is an unambiguous when-to-use rule tied to concrete alternatives, leaving nothing to inference.

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