Skip to main content
Glama

tts_config

View and change text-to-speech settings: enable or disable narration, toggle auto-speak, choose a voice, and adjust playback speed.

Instructions

View or change TTS settings. Call with no parameters to see current config. Use to: enable/disable TTS, turn auto-speak on/off (auto-speak makes Claude speak every response), change voice, change speed. When the user says 'mute tts', 'unmute tts', 'tts on', 'tts off', 'stop speaking', 'start speaking', 'auto speak', 'speak all responses', 'change voice', or 'change speed' — use this tool.

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

Input Schema

NameRequiredDescriptionDefault
autoNotrue = Claude should call speak on every response automatically. false = only speak when explicitly asked.
speedNoPlayback speed multiplier (0.5 to 2.0, default 1.0)
voiceNoKokoro voice ID. Prefix guide: af/am=American English, bf/bm=British English, ef/em=Spanish, ff=French, hf/hm=Hindi, if/im=Italian, jf/jm=Japanese, pf/pm=Portuguese, zf=Mandarin. f=female, m=male.
enabledNotrue to enable TTS, false to disable (mute/unmute)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations, the description carries the full behavioral burden. It discloses the no-argument read behavior and clarifies the meaning of auto-speak, but says nothing about whether changes persist, whether they apply only to the current session, or whether any permissions are needed for a mutating config tool.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

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

The purpose and read behavior are front-loaded, which is good. The trigger-phrase list, however, repeats capabilities already listed earlier ("enable/disable TTS" versus 'tts on'/'tts off') and makes the description noticeably longer than needed.

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 four-parameter, all-optional config tool with no output schema, the description covers both the read and write modes and each setting's effect. The remaining gap is the return shape and persistence semantics, which is minor for a low-risk settings tool.

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 description coverage is 100% and the schema already explains `auto`, `speed` range, and the voice ID prefixes in detail. The description adds only the no-parameter read convention and a plain-language gloss on auto-speak, so baseline 3 is appropriate.

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?

The description states a specific verb and resource ("View or change TTS settings") and enumerates the settings it can change. It clearly contrasts configuring TTS with producing speech, but never names the sibling tool `speak` as the alternative for actual speech output.

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 explains the read path ("Call with no parameters to see current config") and gives a concrete set of user phrases that should route here. It stops short of stating when NOT to use this tool or pointing to `speak` for speaking, so there are no exclusions.

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