Skip to main content
Glama
Sign In
MCP Make Sound

MCP Make Sound

by nocoo
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

play_sound

Play system sounds, text-to-speech audio, or custom audio files to provide audio feedback in applications.

Instructions

Play various types of sounds with customizable parameters

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "type": "<type>"
    },
    "name": "play_sound"
  }
}

Input Schema

NameRequiredDescriptionDefault
typeYesType of sound to play
nameNoSystem sound name (required when type is "system")
textNoText to speak (required when type is "tts")
voiceNoVoice name (optional, used with type "tts", uses system default if not specified)
pathNoAbsolute path to audio file (required when type is "file")

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.6/5.0
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It mentions 'customizable parameters' but fails to explain key traits like whether playback is blocking or non-blocking, error handling (e.g., if a file path is invalid), or system dependencies (e.g., TTS availability). This leaves significant gaps in understanding the tool's behavior.

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 description is a single, efficient sentence that front-loads the core purpose ('play various types of sounds'). It avoids redundancy but could be more structured by explicitly mentioning the parameter types (e.g., system, TTS, file) to enhance clarity without adding unnecessary length.

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 the complexity of handling multiple sound types (system, TTS, file) with no annotations or output schema, the description is incomplete. It lacks details on behavioral aspects like playback effects, error responses, or how outputs are handled, making it insufficient for safe and effective use by an AI agent.

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?

The input schema has 100% description coverage, providing clear details for all parameters, including enums and requirements. The description adds minimal value beyond this, as it only vaguely references 'customizable parameters' without elaborating on their semantics or interactions, aligning with the baseline score for high schema coverage.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states the tool 'play[s] various types of sounds with customizable parameters', which clarifies the action (play) and resource (sounds) but is vague about scope and differentiation. It does not specify what 'various types' means or how it differs from sibling tools like play_error_sound, leaving room for ambiguity.

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, such as the sibling tools (play_error_sound, play_info_sound, play_warning_sound). The description implies general sound playback but offers no context for choosing between this and more specific tools, leading to potential misuse.

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