Gomo Sounds

Create entity

create_entity

Creates an entity in a game: a THING that exists in the game and makes noise (unit, enemy, building, object, block, character, button or screen). NEVER an action or moment: 'Undo', 'Snap', 'Level complete', 'Jump' are EVENTS of something (of Interface, of Blocks, of the Character), not entities. Inside a folder, it inherits the folder's events. On the site it is not a card: it shows as a label (image and name) on the cards of its sounds, so to the user say 'the Player's sounds', not 'entity'.

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": "<name>"
    },
    "name": "create_entity"
  }
}

Input Schema

Name	Required	Description
`name`	Yes
`game_id`	Yes
`folder_id`	No	Folder (see list_folders). Without it, the entity goes into Sound effects.
`description`	No	How it sounds; goes into the prompts.
`external_id`	No	The engine scene of this thing (e.g. res://player/player.tscn). With it, the plugin sync merges into this entity instead of creating another: create entities before the sync without fear of duplicates.

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 11, 2026

TDQS

A3.9/5.0

Behavior3/5

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

With only a title annotation and no readOnly/destructive hints, the description carries the behavioral burden. It usefully discloses folder event inheritance, site presentation as a label, and external_id sync merging, but it omits permissions, error conditions, and what the creation returns.

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 definition is front-loaded with the core action and its entity taxonomy, then adds folder and UI context. The instruction about telling users 'the Player's sounds' is somewhat tangential to invoking the tool, keeping it from a perfect score, but the overall structure is clear.

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 five-parameter creation tool with no output schema and minimal annotations, the description covers purpose, entity-versus-event classification, folder inheritance, sync behavior, and UI semantics. It still lacks return-value and failure-mode information, which prevents a 5.

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 60%, and the schema already documents folder_id's default destination and external_id's sync-merging behavior. The description adds inheritance semantics for folders and user-facing labeling context, but adds little syntax or meaning for name, game_id, or description beyond the schema.

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: 'Creates an entity in a game.' It defines what an entity is with concrete examples and explicitly excludes non-entities such as actions and moments, which distinguishes it from the sibling create_event even though that tool is not 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?

Gives clear decision criteria for when something is an entity versus an event, including worked examples like 'Undo' and 'Jump'. It does not explicitly name create_event as the alternative tool, nor does it state prerequisites such as game existence or permissions, so it falls short of full routing guidance.

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?