Gomo Sounds

Game export link

export_game

Read-only

For the user to download all the chosen sounds at once (other engines, or when they ask). Link to the .zip with the game's CHOSEN sounds and the manifest.json (neutral format for any engine): show it to the user, who opens it in any browser (it works for 24 hours). In Godot, the plugin installs it directly. An event with more than one sound (e.g. 3 sword hits) must be played by picking one of its files at random each time, never only the first: write the playback code that way and tell the user.

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": {
      "game_id": "<game_id>"
    },
    "name": "export_game"
  }
}

Input Schema

Name	Required	Description	Default
`game_id`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 11, 2026

TDQS

A3.6/5.0

Behavior4/5

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

Annotations only declare readOnlyHint=true; the description adds genuinely new behavior: the link expires after 24 hours, the user must be shown the link and opens it in a browser, and the Godot plugin can install the archive directly. These are material facts about a time-limited, user-facing artifact that no structured field conveys.

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

Conciseness2/5

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

The purpose and delivery constraints are front-loaded, but the final sentence about randomly picking among multiple sounds for an event is playback-code guidance unrelated to invoking this export tool and consumes a large share of the text. The parenthetical asides ('other engines, or when they ask') add noise without adding decision value.

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 single-parameter, no-output-schema tool, the description covers what is produced (zip + manifest), the lifetime, and how the user consumes it. The only real gap is that the return value type (a URL string vs. a structured object) is not stated.

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?

There is one parameter, game_id, with 0% schema description coverage. The description implies the export is scoped to 'the game's CHOSEN sounds', which indirectly identifies the parameter, but never states that game_id selects the game, gives its format, or explains what happens for a game with no chosen sounds.

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 concrete outcome: a link to a .zip containing the game's chosen sounds plus a manifest.json in a neutral format. The verb is implicit (export/return a download link) but the deliverable is unambiguous, and the Godot-plugin remark implicitly distinguishes it from the godot_plugin sibling.

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 a clear trigger — 'For the user to download all the chosen sounds at once (other engines, or when they ask)' — and hints that in Godot the plugin path is used instead. There is no explicit 'do not call this when...' exclusion, but the context is specific enough to route the agent.

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?