Skip to main content
Glama
elad12390

notification-mcp

by elad12390
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

notify

Sends a spoken audio alert when a task completes, so you don't have to watch the screen. Uses AI voices to deliver the message.

Instructions

Sends a notification to the user. Use this when you complete a task and want to alert the user.

IMPORTANT - Writing expressive messages:

  • Use punctuation naturally: "Hello!" sounds excited, "Hello..." sounds thoughtful

  • Use commas for pauses: "Well, I think so" has a natural pause

  • Use ellipsis for longer pauses: "Wait... what?"

  • Exclamation marks add energy: "Great job!" vs "Great job."

  • Question marks affect intonation: "Really?" sounds curious

  • Break long messages into sentences for natural rhythm

  • The model reads punctuation expressively, so write like you'd want it spoken!

Example good messages:

  • "Hey! Your task is complete. Everything went smoothly."

  • "Hmm... I found something interesting. Check this out!"

  • "Done! The build succeeded, and all tests passed."

CUSTOM PRONUNCIATION (IPA): For words that need specific pronunciation, use: [word](/IPA phonemes/) Common IPA symbols:

  • χ = Hebrew ח (chet), guttural "kh" sound

  • ʃ = "sh" sound

  • ð = "th" in "the"

  • θ = "th" in "think"

  • ŋ = "ng" sound

  • ɹ = American "r"

Examples:

  • "Chaim" - Hebrew name with guttural ח

  • "Elad" - Pronounce as "eh-lahd"

  • "Hello world!" - Custom pronunciation for "world"

TTS ENGINE OPTIONS (set via NOTIFICATION_METHOD env var):

  • "kokoro" (default): Fast (~3-5s), built-in voices, IPA pronunciation support

  • "f5tts": Higher quality (flow matching), slower (~10-15s), voice cloning capable

  • "say": macOS built-in, fastest but robotic

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
titleNoOptional title for the notification (spoken before the message with a pause)
voiceNoVoice to use. For Kokoro: heart, bella, nicole, sarah, adam, michael, emma, george (or full names like af_heart, bm_george). For macOS say: Samantha, Daniel, etc. For F5-TTS: uses bundled voice or custom via F5TTS_REF_AUDIO env.
messageYesThe notification message. Write naturally with punctuation for expressive speech: use '!' for excitement, '...' for pauses, ',' for brief pauses, '?' for questions. Example: 'Hey! Your task is done. Everything worked perfectly.'
reasoningYesExplain why you are using this tool - helps track usage patterns and optimize the server

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv3.0.0

TDQS

A3.5/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 does add genuine operational context — the NOTIFICATION_METHOD env var, per-engine latency (~3-5s vs ~10-15s), and voice-cloning capability — but says nothing about failure behavior, permissions, or whether the call blocks until speech finishes.

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 is correctly front-loaded, but the body is heavily padded: the punctuation/expressiveness section restates guidance already present in the message parameter's schema description, and stacks multiple redundant examples. Only the IPA syntax and TTS engine sections clearly earn their length.

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

Completeness3/5

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

For a 4-parameter tool with no annotations and no output schema, the description covers configuration and message formatting but omits what happens on failure, whether delivery is synchronous, and any environment prerequisites beyond the engine choice. Adequate but with visible holes.

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 the voice, message, title, and reasoning parameters are already documented. The description's IPA notation syntax ('[word](/IPA phonemes/)') and symbol table are genuinely absent from the schema, but they only apply to the message payload rather than adding semantics for the parameters themselves, keeping this near the baseline.

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 first two sentences give a specific verb and resource ('Sends a notification to the user') plus the triggering condition ('when you complete a task and want to alert the user'). It is clear what the tool does, but it never differentiates itself from the sibling report_issue, so an agent must infer the boundary.

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?

'Use this when you complete a task and want to alert the user' supplies an explicit trigger condition. There are no when-not conditions and no routing guidance relative to report_issue, so the guidance is clear but incomplete.

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