Gomo Sounds

Delete a sound or a track

delete_sound

Destructive

Deletes a sound (event) or a track for good, with its versions, like the Delete button on its page: the game stops playing it. Versions that are favorites or also chosen in another sound stay there. While it has a generation queued or running, it is refused: wait for it (job_status). ONLY when the user asked, in this conversation, to delete THIS sound (say its name and game before); never to tidy up on your own, never several at once without listing them and getting a yes. name must be the sound's current name, as a check.

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": {
      "event_id": "<event_id>",
      "name": "<name>"
    },
    "name": "delete_sound"
  }
}

Input Schema

Name	Required	Description	Default
`name`	Yes	The sound's current name (from find_sounds or list_folders): if it does not match, nothing is deleted.
`event_id`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 11, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already declare destructiveHint=true, and the description adds substantial context beyond that: versions are removed but favorited or reused versions survive, deletion is refused while a generation job is queued or running, and the name is a safety check. It does not describe the response or how to recover a mistaken deletion, but the mutation's blast radius is clearly drawn.

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?

Front-loaded with the action and its effect, then edge cases (favorites survive, queued generation blocks), then the authorization policy. Dense and mostly earning its sentences, though the UI-metaphor aside and the repeated confirmation rule cost some space.

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 destructive two-parameter tool with no output schema, the definition covers side effects, refusal conditions, blocked-state alternative, and required user consent. Only the undocumented event_id parameter and post-call outcome remain 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 50%: name is documented in the schema and reinforced here ('name must be the sound's current name, as a check'), but event_id is undocumented in both schema and description, and the description adds nothing about the name/game pairing it mentions conversationally. The partial coverage gap is only partly compensated.

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?

States a specific verb and resource ('Deletes a sound (event) or a track'), scopes it ('for good, with its versions'), and contrasts the effect with the UI metaphor ('like the Delete button on its page: the game stops playing it'), so an agent can distinguish it from save_sound or move_entities without opening a schema.

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?

Gives explicit when-to-use and when-not-to-use rules: only when the user asked in this conversation to delete THIS sound, never to tidy up unprompted, never several at once without listing and confirmation. It also names the blocking condition and the alternative to consult first ('wait for it (job_status)'), which is precisely the routing guidance an agent needs.

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

All Gomo Sounds tools Inspect

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

Need Help?