Invoke any method on a node in the running Godot game, passing optional arguments to control gameplay in real time.
Call a method on any node in the running game with optional arguments
| Name | Required | Description | Default |
|---|---|---|---|
| args | No | Optional array of arguments to pass to the method | |
| method | Yes | Method name to call | |
| nodePath | Yes | Path to the node |
Changes observed during successful MCP inspections.
v1.0.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are present, so the description must carry the full burden of behavioral disclosure. It does not warn that invoking an arbitrary method can mutate game state, fail at runtime, or produce side effects depending on the method called.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
One tight sentence with no filler, and the core action and target are front-loaded. Every word earns its place.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For an arbitrary method-invocation tool with no output schema and no annotations, the description omits key operational details such as whether the method's return value is returned and what failure modes exist. This makes the tool riskier to invoke blindly.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 100%, so the schema already documents all three parameters. The description's mention of optional arguments adds no meaning beyond the existing args property.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
States a specific action ('Call a method') applied to a concrete resource ('any node in the running game') and mentions optional arguments. This clearly distinguishes it from sibling property get/set tools and arbitrary expression evaluation tools.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
No guidance is given on when to use this tool versus alternatives like game_eval, game_set_property, or other node-specific tools, and no exclusions are provided. Usage is only implied by the action itself.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.