Skip to main content
Glama
Sign In
mac-voice-mcp

mac-voice-mcp

by jeet0007
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Voice setup

voice_setup
Idempotent

Checks for required text-to-speech, microphone, speech-to-text, and model dependencies, then optionally installs any missing components.

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. bubble=true (also only after the user agrees) builds the floating call bubble on this Mac with swiftc: a small window during calls with mute and hang up. If it reports INSTALLING, the install continues in the background — wait a minute and call it again to check.

Input Schema

NameRequiredDescriptionDefault
bubbleNotrue: build the floating call bubble on this Mac with swiftc (about 10 s; macOS). Ask the user first.
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.9.0
    • addedInput schema / properties / bubble
      Added value: +{
+  "description": "true: build the floating call bubble on this Mac with swiftc (about 10 s; macOS). Ask the user first.",
+  "type": "boolean"
+}
  2. 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"
+}
  3. First observedv0.1.0

TDQS

A4.1/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, idempotentHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is partly covered. The description still adds real behavior: existing installs are reused, a model found elsewhere on disk is symlinked rather than re-downloaded, brew install runs for missing packages only, and nothing is ever uninstalled. The one notable gap is what the check actually returns beyond the INSTALLING state.

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?

The purpose is front-loaded in the first clause and each following sentence covers a distinct concern: reuse of existing installs, the consent gate, kokoro, bubble, and the background INSTALLING state. The main defect is redundancy with the schema — the ~1 GB Kokoro size and 'ask the user first' warnings appear twice — plus an odd line-break inside the first sentence.

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 three-flag, open-world setup tool with no output schema, it covers the essentials: prerequisites, consent, side effects, non-destructiveness, and the asynchronous INSTALLING state. What it does not specify is the shape of the check result (how the missing pieces are reported), which is the one thing an agent must parse on the very first call.

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 coverage is 100%, so all three booleans are already described in the input schema, including the 'ask the user first' caveat. The description adds workflow meaning ('install=false is the default, call it first') and the post-install consequence that Kokoro is used automatically with the built-in voice as fallback, but it largely restates the schema's own parameter text, so a baseline 3 is right.

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 description names a specific verb+resource: checks the machine for the prerequisites speak_and_listen needs (TTS, SoX, whisper.cpp, speech model) and optionally installs what is missing. It explicitly ties itself to the sibling speak_and_listen, so an agent can place it in the tool set without opening a schema.

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?

It gives a hard ordering rule: call with install=false (the default) first, report what is missing, and only then call install=true after the user agrees. It extends the same consent gate to kokoro and bubble, and adds a re-entry rule for the INSTALLING state (wait a minute and call again).

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