Skip to main content
Glama
Godot MCP - Full Control
by cxb2523

game_rpc

Call or configure RPC methods on nodes to manage networked communication, specifying arguments, mode, sync, channel, and node path.

Instructions

Call or configure RPC methods on nodes

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": {
      "nodePath": "<nodePath>",
      "action": "<action>",
      "method": "<method>"
    },
    "name": "game_rpc"
  }
}

Input Schema

NameRequiredDescriptionDefault
argsNoArguments for the RPC call
modeNoRPC mode: any_peer, authority
syncNoSync mode: call_local, call_remote
actionYesAction: call, configure
methodYesMethod name
channelNoTransfer channel
nodePathYesPath to the node

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv3.1.0

TDQS

C2.6/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full burden and discloses almost nothing. It does not say whether configure mutates node state irreversibly, what permissions or network context are needed, what happens on an invalid method, or whether a result is returned. "Configure" implies mutation with no disclosure of its effects.

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?

It is a single short, front-loaded sentence with no wasted words. Brevity here edges toward under-specification rather than verbosity, but on the conciseness axis itself the phrasing is clean.

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

Completeness2/5

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

For a seven-parameter tool with three required fields, two operational modes, no annotations, and no output schema, a seven-word description is inadequate. Nothing explains the call/configure branch, the interaction of mode/sync/channel with a call, or what the agent gets back.

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 100%, so parameter meaning is largely documented in structured data; the baseline is 3. The description adds only the framing that these methods live on nodes, and it does not clarify which parameters apply to the "call" action versus the "configure" action, which is the main ambiguity in this seven-parameter tool.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a specific verb pair ("call or configure") and a resource ("RPC methods on nodes"), so the basic purpose is recoverable. However, it does not distinguish this from close siblings like game_call_method, game_multiplayer, or game_connect_signal, and "RPC" is left unqualified, so an agent cannot confidently route between them from the description alone.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no when-to-use guidance, no prerequisites (e.g., that the game must be running or that multiplayer setup is required), and no mention of alternatives. The two-mode split between "call" and "configure" is only inferable from the schema's action parameter, not the description.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools