Skip to main content
Glama
Sign In
Suzu (鈴) - Claude Code Notification Server

Suzu (鈴) - Claude Code Notification Server

by denar90
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

notify

Display desktop notifications with sound to alert users when Claude Code completes tasks, supporting macOS, Linux, and Windows systems.

Instructions

Show a general notification with sound

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

Input Schema

NameRequiredDescriptionDefault
titleNoNotification titleClaude Code
messageNoNotification messageNotification from Claude
sound_typeNoType of notification sound to playinfo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.9/5.0
Behavior2/5

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

With no annotations, the description carries full burden but only states it shows a notification with sound. It doesn't disclose behavioral traits such as user interaction effects, platform dependencies, or whether it's blocking/non-blocking, leaving significant gaps.

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

Conciseness5/5

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

The description is a single, efficient sentence with zero waste, clearly front-loaded and appropriately sized for the tool's simplicity.

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

Completeness2/5

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

Given no annotations and no output schema, the description is too minimal. It lacks details on behavior, error handling, or visual/auditory effects, making it incomplete for a notification tool with potential user impact.

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%, so the schema fully documents parameters. The description adds no additional meaning beyond implying sound is involved, aligning with the baseline for high schema coverage.

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 clearly states the action ('Show') and resource ('general notification with sound'), making the purpose understandable. It doesn't specifically differentiate from siblings like 'question_alert' or 'test_sound', which prevents a perfect score.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance is provided on when to use this tool versus alternatives like 'question_alert' or 'test_sound'. The description implies general notifications but lacks explicit context or exclusions for usage.

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