Skip to main content
Glama
Sign In

Notify Sound

by io.github.botmonster
OverviewDiscussionsAdmin

List built-in sounds

list_library_sounds
Read-onlyIdempotent

List the built-in sounds by group, or search them by name. Without arguments it lists every group with its sound names. Use a close built-in sound as a starting point.

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

Input Schema

NameRequiredDescriptionDefault
groupNoOnly this group, with each sound described.
queryNoSearch sound names, e.g. "bell" or "coin".

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive/closed-world, so the safety bar is low. The description still adds real behavior beyond them: with no arguments the result is every group with its sound names, and with a group set each sound is described. Missing only output volume/pagination expectations, which is minor for a static built-in catalog.

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?

Three short sentences, front-loaded with the core action, and the default behavior comes before the usage tip. The phrase 'or search them by name' is slightly redundant with the schema's query description, a small amount of waste.

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?

For a two-optional-param, read-only listing tool with full annotation coverage and full schema descriptions, the description supplies what structured fields cannot: the no-argument default and a reason to use it. Only the both-parameters-specified case is left unaddressed.

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% and the enum for group is fully documented with per-parameter descriptions, so the baseline is 3. The description adds the zero-argument default (list all groups) which the schema can't express, but adds nothing about how group and query combine when both are supplied.

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?

States a specific verb and resource ('List the built-in sounds'), plus the two axes of retrieval (by group or by name search). It doesn't name any sibling, so an agent must infer the split with get_library_sound / get_sound_guide on its own, which keeps it out of 5 territory.

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

Usage Guidelines3/5

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

'Use a close built-in sound as a starting point' gives a reason to call it, and the no-argument case is spelled out. But there is no explicit when-not and no pointer to the obvious alternative for retrieving a single sound's full definition (get_library_sound), leaving routing to inference.

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

All Notify Sound toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources