Skip to main content
Glama
Sign In
sound-mcp

sound-mcp

by giuliocapecchi
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

play_sound

Play notification sounds to alert users when background tasks finish.

Instructions

Play a notification sound.

name can be a registered sound (see list_sounds) or an absolute path to an audio file. If omitted, plays the configured default.

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

Input Schema

NameRequiredDescriptionDefault
nameNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.4/5.0
Behavior3/5

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

Without annotations, the description must explain behavior. It discloses the parameter options and default, but does not cover edge cases like error handling, blocking versus non-blocking execution, or file compatibility, limiting full transparency.

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 extremely concise (two sentences) and front-loaded with the core action. Every sentence is meaningful and contributes to understanding, with no waste.

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?

Given the tool's simplicity (one optional parameter) and the existence of an output schema, the description is complete. It covers the purpose, parameter semantics, default behavior, and references a sibling tool, leaving no major gaps for an AI agent.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With 0% schema description coverage, the description fully compensates by explaining the 'name' parameter in detail: it can be a registered sound (linking to list_sounds) or an absolute path, and it is optional with a default. This adds significant value beyond the schema.

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 clearly states the tool's function: 'Play a notification sound.' It is specific and distinct from siblings like list_sounds and notify, ensuring the agent can select it appropriately.

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?

The description provides guidance by mentioning list_sounds for registered sounds and explaining default behavior. However, it lacks explicit when-not-to-use or comparison with the notify sibling, which would improve decision-making.

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