No user-submitted related servers found.
Scored across 3 tools
Each tool maps to a distinct action on the voice output system: producing speech, halting it, and inspecting system state. There is no plausible way to confuse speak with stop or status, and the descriptions reinforce the boundaries.
All three tools use the same snake_case `voice_` prefix followed by a concise action/state noun (speak, stop, status). The pattern is entirely predictable and readable.
Three tools is a tight, well-scoped surface for a narrow domain (TTS output control). Every tool earns its place: emit audio, cancel audio, check readiness — nothing is redundant or missing at this granularity.
The core lifecycle (play, stop, inspect status) is covered, which handles the main agent workflows including silence-on-request. Minor gaps exist for peripheral needs like listing available providers/voices or queueing/pausing, but these are workable around via the speak overrides.