Skip to main content
Glama
Sign In

Notify Sound

by io.github.botmonster
OverviewDiscussionsAdmin

Create a sound

create_sound

Build a notification sound from your own layer design and get an editor link for it. The link opens the sound in the editor, where the user plays, tweaks and downloads it. Returns the link, the stored sound and warnings for any value that was out of range, rounded or ignored. Read get_sound_guide first.

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": {
      "layers": "<layers>"
    },
    "name": "create_sound"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNoName. Sound name, up to 32 characters.
effectNoOne effect over the whole sound.
layersYesLayers play together, each from its own Start after. Leave out any field at its default. Up to 16 layers.
durationNoNote length. How long each note is held, shared by every layer and every repeat. Unit: s. Range 0.003 to 5, step 0.001, default 0.1.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare this is a non-readonly, non-idempotent, non-destructive write. The description adds genuinely new behavior: it returns an editor link plus the stored sound, and out-of-range values are rounded or ignored with warnings rather than rejected. It does not say whether repeated calls create duplicate sounds, but that is largely covered by idempotentHint=false.

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 tight sentences, front-loaded with the action and result. The final "Read get_sound_guide first" is useful but tacked on at the end rather than stated up front with the prerequisite context.

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?

With no output schema, the description correctly explains what comes back (link, stored sound, warnings). For a tool with a 4-parameter nested schema this is nearly complete; only the editor-link lifecycle (does the link expire, does the sound persist unbidden) is 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 description coverage is 100% and each layer field carries units, ranges and defaults, so the burden is already met structurally. The description only says "layer design" and adds no semantics beyond the schema, which is the baseline 3 case.

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 states a specific verb and resource ("Build a notification sound from your own layer design") and adds the distinctive output (an editor link). It is clearly a creation tool, cleanly separable from the read/list siblings (read_sound, list_library_sounds, get_library_sound).

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?

It gives an explicit prerequisite sequence: "Read get_sound_guide first," which is actionable routing to a named sibling. It stops short of stating when not to use it (e.g., when the user wants an existing library sound instead), so it is strong context but not full when/when-not guidance.

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