Gomo Sounds

Send engine scenes

sync_scenes

Idempotent

For engine plugins: sends the project's scenes (up to 20 per call) to the game's Inbox, matching by the engine id (externalId, e.g. res://units/spider.tscn). A scene that is already an entity only gets its image refreshed; a new one waits in the Inbox until the user places it in a tab on the site. Sending again never duplicates.

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

Input Schema

Name	Required	Description	Default
`items`	Yes
`game_id`	Yes

Output Schema

Name	Required	Description	Default
`skipped`	Yes
`entities`	Yes
`inboxMax`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 11, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Beyond idempotentHint it discloses the full lifecycle: existing entities get only their thumbnail refreshed, new scenes stage in the Inbox until manually placed, and re-sends never duplicate. That tells the agent the side effects and the fact that nothing is auto-placed, which the annotation alone does not convey.

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

Conciseness5/5

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

Three tight sentences, front-loaded with audience and action, then consequences, then dedupe guarantee. The only mild redundancy is 'up to 20 per call', which the schema's maxItems already encodes.

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?

An output schema exists so return values need not be described, and the description covers the write semantics thoroughly for a 2-parameter tool. Gaps are minor: no mention of required permissions or failure behavior for invalid or oversized payloads.

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 description coverage is 0%, so the description carries the burden, and it explains the most ambiguous parameter well: externalId is the engine id with a concrete example (res://units/spider.tscn). It also implies the image field via 'image refreshed', but leaves name and description fields, and the game_id target, unexplained.

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 (sends), resource (the project's scenes), destination (the game's Inbox) and audience (engine plugins), with the matching key spelled out. It is clearly distinguishable from siblings such as place_scenes or game_scenes because it routes content into an Inbox rather than acting on placed entities.

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?

The 'For engine plugins' opener scopes when this tool applies, and the Inbox lifecycle explains what happens after the call. It stops short of naming an alternative (e.g. place_scenes) or stating exclusions, so the agent must infer the boundary from sibling names.

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?