Skip to main content
Glama
Godot MCP Server

Godot MCP Server

by neondeex

call_game_node_method

Invokes a method on a specified node in a running Godot game, passing arguments to trigger in-game behavior from Claude Code.

Instructions

Call a method on a node in the running 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": {
      "node_path": "<node_path>",
      "method": "<method>"
    },
    "name": "call_game_node_method"
  }
}

Input Schema

NameRequiredDescriptionDefault
argsNoArguments to pass to the method
methodYesMethod name to call
node_pathYesNode path in the running game

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.8/5.0
Behavior2/5

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

With no annotations, the description carries the full behavioral burden, and it discloses almost nothing: not whether the call mutates game state, not what happens if the method does not exist or throws, not whether the call is synchronous or how long it may block, and not what value is returned. 'Running game' is the only real behavioral signal.

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?

A single front-loaded sentence with zero wasted words, so structure is clean. The terseness is under-specification rather than verbosity, which does not penalize conciseness itself.

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

Completeness1/5

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

For an unannotated, arbitrary-argument RPC-style tool with no output schema, the agent needs to know mutation risk, failure modes and return semantics, and none of that is present. The definition is far too thin relative to the tool's open-ended nature.

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 description coverage is 100%, so node_path, method and args are already documented in the schema; the description adds no syntax details such as path format (e.g. absolute scene-tree path), method-name casing, or how args are marshalled. Baseline 3 applies when the schema does the heavy lifting.

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?

"Call a method on a node in the running game" names a specific verb (call), resource (node in the running game) and target (method), which separates it from set_game_node_property or get_game_node_properties. It stops short of explicitly naming when to prefer execute_game_script, so sibling differentiation is only implied.

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 or when-not-to-use guidance, and no mention of prerequisites such as the node existing or the game being paused/running. The only hint is 'in the running game', which suggests a live runtime context but leaves the choice against execute_game_script or set_game_node_property unaddressed.

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