Skip to main content
Glama
tijs

MCP Sound Tool

by tijs

list_available_sounds

Discover available notification sounds to verify sound options and select appropriate audio feedback for coding environments.

Instructions

    List all available notification sounds.
    
    WHEN TO USE THIS TOOL:
    - When you need to check what sound options are available
    - When determining if a specific sound file exists
    - Before using a custom sound to verify available options
    
    This tool helps you discover what sounds are available for providing audio feedback.
    

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • The handler function that implements the core logic of the 'list_available_sounds' tool by listing .mp3 and .wav files from the configured sounds directory.
    def list_available_sounds() -> str:
        try:
            sounds = [f for f in os.listdir(self.sounds_dir) if f.endswith(('.mp3', '.wav'))]
            if sounds:
                return "Available sounds:\n" + "\n".join(sounds)
            else:
                return "No sound files found in the sounds directory."
        except Exception as e:
            return f"Error listing sounds: {e}"
  • The @self.mcp.tool decorator that registers the list_available_sounds function as an MCP tool, including usage description.
    @self.mcp.tool(description="""
    List all available notification sounds.
    
    WHEN TO USE THIS TOOL:
    - When you need to check what sound options are available
    - When determining if a specific sound file exists
    - Before using a custom sound to verify available options
    
    This tool helps you discover what sounds are available for providing audio feedback.
    """)
  • JSON schema definition for the list_available_sounds tool specifying no input parameters and string return.
    list_sounds_tool_definition = {
        "name": "list_available_sounds",
        "description": """
        List all available notification sounds.
        
        Use this tool when you need to check what sound options are available to play.
        This is helpful when determining what custom sounds might be available.
        """,
        "parameters": {
            "type": "object",
            "properties": {},
            "required": []
        },
        "returns": {
            "type": "string",
            "description": "A string listing all available sound files"
        }
    }
Behavior3/5

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

No annotations are provided, so the description carries the full burden. It mentions the tool helps 'discover what sounds are available for providing audio feedback,' which implies a read-only operation, but doesn't explicitly state behavioral traits like whether it requires authentication, has rate limits, or what format the output takes. It adds some context but lacks comprehensive behavioral disclosure.

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 well-structured with clear sections, front-loads the purpose, and every sentence adds value without redundancy. It efficiently conveys necessary information in a compact format.

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?

Given the tool's simplicity (0 parameters, output schema exists), the description is mostly complete. It covers purpose and usage guidelines effectively. However, without annotations, it could benefit from more behavioral details like output format or error handling, though the output schema mitigates some of this gap.

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

Parameters4/5

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

The input schema has 0 parameters with 100% coverage, so no parameter documentation is needed. The description appropriately doesn't discuss parameters, focusing instead on usage context. This meets the baseline for tools with no parameters.

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 specific action ('List all available notification sounds') and resource ('notification sounds'), distinguishing it from sibling tools like 'install_to_user_dir' and 'play_sound' which perform different operations. The purpose is unambiguous and well-defined.

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?

The description includes an explicit 'WHEN TO USE THIS TOOL' section with three specific scenarios: checking available sound options, determining if a specific sound file exists, and verifying options before using a custom sound. This provides clear guidance on when to use this tool versus alternatives.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/tijs/py-sound-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server