Gomo Sounds

Sounds installed in the engine

mark_installed

Idempotent

For engine plugins: tells the site the chosen sounds were installed in the project now, so the site can show which changes already reached the game.

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": "mark_installed"
  }
}

Input Schema

Name	Required	Description	Default
`game_id`	Yes

Output Schema

Name	Required	Description	Default
`id`	Yes
`installedAt`	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?

Beyond the supplied idempotency annotation, the description discloses that the operation communicates installation status to the site so its display can reflect changes that reached the game. The wording also implies status reporting rather than file installation, although it does not explain what happens if no sounds are selected.

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?

The single sentence front-loads the engine-plugin context and efficiently connects the action to its purpose. Phrases such as “now” and “already reached” are slightly conversational and redundant, but do not substantially obscure the meaning.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

This is adequate for understanding the basic post-installation call, and the output schema removes the need to describe return values. However, because there are no sound parameters, the unexplained phrase “the chosen sounds” leaves a core gap: how the tool determines which installations to report and whether one call covers the whole current selection.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The sole parameter, game_id, has no schema description, and the description never explicitly defines it, its format, or where to obtain it. References to “the project” and “the game” only indirectly suggest that it identifies the game whose installation status should be updated.

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 clarifies that the tool reports chosen sounds as installed to the site, rather than generating or installing the sounds itself. The engine-plugin scope and synchronization purpose are clear, though no sibling tool or boundary case is named.

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?

“For engine plugins” and “were installed in the project now” establish both the intended caller and that the call belongs after installation. It does not provide exclusions, prerequisites for the sound selection, or an alternative for non-plugin workflows.

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?