Skip to main content
Glama
Sign In

Notify Sound

by io.github.botmonster
OverviewDiscussionsAdmin

Read a share link

read_sound
Read-onlyIdempotent

Turn a share link (or the code after #s=) back into the sound design, to change it and call create_sound again.

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": {
      "link": "<link>"
    },
    "name": "read_sound"
  }
}

Input Schema

NameRequiredDescriptionDefault
linkYesA share link, "#s=..." or the bare code.

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 establish that this is a safe, read-only, idempotent, closed-world operation. The description adds useful context about the input forms and what the operation reconstructs, plus the intended edit-and-recreate workflow, though it does not cover error behavior for invalid links.

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 a single front-loaded sentence with no wasted wording. It puts the core decoding action first and then adds the practical follow-up workflow.

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?

For a simple one-parameter read/decode tool, the description, annotations, and fully described schema together give enough context to call it correctly. It also communicates the essential return concept by saying it reconstructs the sound design.

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% for the single link parameter, and the schema itself documents the share link, '#s=...' form, and bare code. The description reinforces the accepted input forms but adds little beyond the schema, so the baseline of 3 is appropriate.

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?

The description states a specific action and resource: turning a share link or bare code back into a sound design. It also distinguishes the tool from create_sound by framing it as the inverse operation, though it does not explicitly contrast with library-reading siblings.

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 gives a clear use case: decode a share link so the sound design can be changed and passed to create_sound again. It names the follow-up tool but does not explicitly state when not to use this tool or name alternatives beyond create_sound.

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