Gomo Sounds

Find sounds

find_sounds

Read-only

Searches entities (units, mobs, buildings, screens) by name, game, event or prompt, ignoring accents/case, and returns EVERYTHING about each one: image, events (Attack, Death...), each generated variation with id, prompt used, duration, cost, date, whether it's the chosen one, the audio URL and the editor link (editUrl), plus the page of the entity and of each event on the site (url). Also finds folder events (music, ambience, interface sounds like 'Main theme' or 'Click') by event name, prompt or folder name. Use it whenever the user talks about the sounds of something (e.g. 'the dragon sounds') or asks for the link of a sound: give the event's url. A track (Music folder) also shows what is saved in its form (track: mode, quality, genre, bpm, key) and the tags of its downloaded file (music: artist, title, album).

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": {
      "query": "<query>"
    },
    "name": "find_sounds"
  }
}

Input Schema

Name	Required	Description	Default
`query`	Yes	Name or part of the name. E.g. 'dragon', 'castle', 'attack'.
`include_images`	No	Attach each entity's image (up to 3).

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 11, 2026

TDQS

A3.6/5.0

Behavior3/5

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

readOnlyHint already establishes that this is a safe lookup, so the bar is lower. The description adds real value by disclosing match normalization (ignores accents/case) and searchable fields (name, game, event, prompt), but says nothing about result volume, limits, or pagination for a tool that claims to return 'EVERYTHING'.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Purpose is front-loaded, but the middle is a single sprawling run-on sentence enumerating return fields (id, prompt, duration, cost, date, chosen flag, audio URL, editUrl, url) that would read far better as a list. The information is largely relevant, but the packing hurts scanability.

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 carries the return-value burden and does so thoroughly: entity image, events, variations, audio URL, editUrl, site URLs, and even track/tag metadata for Music folder items. Only the lack of any statement about result caps or pagination leaves a gap.

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%, so baseline is 3. The description does add meaning beyond the schema's 'Name or part of the name' by widening the query target to game, event and prompt and noting accent/case insensitivity, which is genuinely useful matching semantics not present in the schema text.

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 ('searches entities (units, mobs, buildings, screens)') and extends it to folder events by name/prompt/folder. It is clear what the tool retrieves, but it never distinguishes itself from plausible siblings such as get_entity or sounds_for_folder, leaving the agent to infer the boundary.

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?

Gives an explicit trigger condition: 'Use it whenever the user talks about the sounds of something (e.g. "the dragon sounds") or asks for the link of a sound', plus the follow-through action (return the event's url). No when-not guidance or named alternative is supplied, so it stops short of a 5.

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?