Skip to main content
Glama
Sign In
MiMo TTS MCP Server

MiMo TTS MCP Server

by haibinwang9
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

MiMo TTS - catalog

list_voices

List available MiMo TTS models, their capabilities, built-in preset voices, and output file locations. Read-only; no API key required.

Instructions

List the MiMo TTS models, their capabilities, built-in preset voices, and where files are written. Read-only; no API key needed.

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": "list_voices"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.9/5.0
Behavior4/5

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

With no annotations, the description carries the behavioral burden and usefully discloses that the operation is read-only and requires no API key. It also indirectly covers return content (models, capabilities, voices, file paths), though it omits error behavior or list stability details, which are minor for a zero-param catalog.

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?

Two tight sentences, front-loaded with the core listing action, and the trailing safety note earns its place. Zero waste.

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 zero-param, no-output-schema catalog tool, the description covers what is listed and the key safety traits. A small gap remains in explicitly routing the agent from discovery to the sibling synthesis tools.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool takes zero parameters, so the baseline is 4. The description adds no parameter details and none are needed.

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 'List' and a detailed resource: MiMo TTS models, capabilities, preset voices, and file output locations. It is clearly a catalog tool distinct from the sibling synthesis/cloning tools, though it does not explicitly name them.

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

Usage Guidelines3/5

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

'Read-only; no API key needed' gives a calling hint, but there is no explicit when-to-use or when-not-to-use guidance relative to text_to_speech, design_voice_to_speech, or clone_voice_to_speech. The implied use is discovering voices before synthesis, but this is left to inference.

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

Deploy Server

Other Tools