Skip to main content
Glama
jeet0007

mac-voice-mcp

by jeet0007
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Voice setup

voice_setup
Idempotent

Verifies your Mac has the speech components (TTS, microphone recorder, speech-to-text, model) needed for voice conversations, and installs missing ones on request.

Instructions

Check whether this computer has everything speak_and_listen needs — text-to-speech, a microphone recorder (SoX), whisper.cpp speech-to-text and the speech model — and optionally install what's missing. Anything already installed is reused (an existing model elsewhere on disk is symlinked, not re-downloaded). Call it with install=false (the default) first and tell the user what is missing. Only call it with install=true after the user agrees: it runs brew install for the missing packages and downloads the speech model once. It never uninstalls or changes anything else. kokoro=true (also only after the user agrees) installs the optional Kokoro voice: more natural than the built-in one, runs on this Mac, about 1 GB on disk. Once installed it's used automatically; the built-in voice stays as the fallback. If it reports INSTALLING, the install continues in the background — wait a minute and call it again to check.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
kokoroNotrue: install the optional Kokoro voice — a natural-sounding neural voice that runs on this Mac (kokoro-js via npm and a one-time model download, about 1 GB on disk). Ask the user first.
installNofalse (default): only check. true: brew install missing packages and download the model. Ask the user first.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.4.0
    • addedInput schema / properties / kokoro
      Added value: +{
+  "description": "true: install the optional Kokoro voice — a natural-sounding neural voice that runs on this Mac (kokoro-js via npm and a one-time model download, about 1 GB on disk). Ask the user first.",
+  "type": "boolean"
+}
  2. First observedv0.1.0

TDQS

A4.8/5.0
Behavior5/5

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

Adds substantial behavior beyond the annotations: existing installs are reused, an existing model is symlinked rather than re-downloaded, brew install runs and the model downloads once, nothing is uninstalled, and it discloses the background INSTALLING state plus the need to re-poll. This is consistent with idempotentHint=true and destructiveHint=false.

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

Conciseness4/5

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

Front-loads the core purpose, then the consent workflow, then the optional kokoro path and the INSTALLING caveat. Slightly long and dense with parentheticals, but each sentence carries distinct operational information and none is filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema and only a hint of the return status, the description compensates by explaining the INSTALLING condition and the re-check loop, so an agent knows what a call will produce and how to proceed. The consent contract and platform assumptions (brew, this Mac) are fully covered for a two-boolean provisioning tool.

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?

Schema coverage is already 100%, so the parameters are documented. The description still adds real meaning the schema lacks: kokoro's size (~1 GB), that it becomes the automatic voice with the built-in one as fallback, and that install=true performs brew install/download in the background. It mostly enriches rather than restating.

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 action (check/install the dependencies speak_and_listen needs) and enumerates exactly which components are involved (TTS, SoX recorder, whisper.cpp, speech model). This clearly distinguishes it from its only sibling, speak_and_listen, which uses rather than provisions those components.

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?

Gives an explicit ordered workflow: call with install=false first and report gaps to the user, only use install=true after user agreement, and only enable kokoro after separate agreement. The when-not conditions (before consent) are stated, not implied.

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