Skip to main content
Glama

List Tts Voices

list_tts_voices
Read-only

查询语音合成当前可用音色清单(code/name/gender/styleTag)。合成前先看这个选 speaker。

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior3/5

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

The annotations already declare readOnlyHint=true, so the safety profile is covered. The description adds the 'currently available' nuance, implying the list is dynamic, but says nothing about whether results are cached or scoped per account. That is acceptable given that an output schema exists.

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 short sentences, front-loaded with the resource and the returned fields, then the actionable guidance. There is no filler and no repetition of the title.

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 zero parameters, a readOnly annotation, and an output schema, the description only needs to establish the purpose and when to call it, and it does that in full. Mentioning the returned fields is slightly redundant with the output schema, but the description otherwise leaves no meaningful gap.

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 schema coverage of 100% and the empty properties object mean there is nothing else to disambiguate. The description correctly adds nothing about parameters, because there are none.

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?

The definition states a specific verb+resource combination: query the currently available TTS voice list, and names the returned fields (code/name/gender/styleTag). The sentence '合成前先看这个选 speaker' implicitly separates it from the synthesize_speech sibling by positioning it as the pre-synthesis lookup step.

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

Usage Guidelines4/5

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

It explicitly says when to call it: before synthesis, to pick a speaker. No exclusion of alternatives is needed here since there is only one enumeration tool, but the definition never states whether the voice list can change or be cached, which keeps it from a 5.

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