Gomo Sounds

Place synced scenes in a tab

place_scenes

Turns scenes waiting in the game's Inbox (sent by the engine plugin; see game_scenes) into entities in a tab, exactly like dragging them on the site. section auto (default) puts each scene by its project path: ui/ or menus/ to Interface, maps/ or levels/ to Ambience, the rest in Sound effects inside a folder named after the project folder (res://units/x.tscn goes to Units). Or choose the tab (ambience, effects, interface) and, inside it, a folder_id. Without item_ids, every scene in the Inbox.

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

Input Schema

Name	Required	Description	Default
`game_id`	Yes
`section`	No	auto (by project path) or the tab: ambience, effects, interface.	auto
`item_ids`	No	Inbox ids from game_scenes. Omitted: all of them.
`folder_id`	No	A folder inside the chosen tab (not with auto). Omitted: the root of the tab.

Output Schema

Name	Required	Description	Default
`placed`	Yes
`entities`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 11, 2026

TDQS

A4.2/5.0

Behavior3/5

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

With only a title annotation, the description carries the full burden, and it does disclose the core side effect (scenes become entities in a tab) and the exact routing rules. It does not say whether items leave the Inbox, what happens on duplicate/conflicting placement, whether syncing must happen first, or anything about error behavior for a bulk write of up to 500 items.

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?

Purpose is front-loaded in the first clause, followed by the routing rules and then the fallback default. Some parenthetical and example material makes it dense, but every sentence conveys a distinct rule rather than restating the schema.

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

Completeness5/5

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

An output schema exists, so return values need not be explained, and the description covers the remaining burden: provenance of inputs, routing semantics, destination folder derivation, and the bulk default. An agent has enough to invoke it correctly in both modes.

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

Parameters4/5

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

Schema coverage is already 75%, yet the description still adds real meaning: the path-to-tab mapping table (ui/ and menus/ to Interface, maps/ and levels/ to Ambience, remainder to Sound effects) and the rule that the destination folder is named after the project folder. It also clarifies the item_ids default, which the schema states only briefly.

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: turning Inbox scenes into entities in a tab, 'exactly like dragging them on the site'. It also names the upstream sibling (game_scenes) that produces the Inbox ids, so an agent can place it in the workflow without opening another schema.

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?

Explains the two operating modes clearly: default 'auto' routing by project path, or an explicit section plus folder_id. It also states the default scope when item_ids is omitted (every scene in the Inbox), which is the main decision an agent faces. It stops short of naming explicit exclusions or prerequisites beyond the plugin reference.

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?