Advance a paused Godot game by one frame for debugging. Works only in windowed sessions; headless games draw no frames, and Godot re-pauses after the next drawn frame.
Advance a paused game by one frame. Windowed sessions only: a headless game never draws a frame, and Godot re-pauses after the next drawn frame.
| Name | Required | Description | Default |
|---|---|---|---|
| session_id | No | Session from runtime_run. Required only when several games run. |
Changes observed during successful MCP inspections.
v1.2.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations declare it non-readonly and non-idempotent, and the description corroborates that by explaining the re-pause behavior and the headless no-op case. It does not cover auth/session requirements or what happens if the game is not paused, so it is solid but not exhaustive.
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?
Two tight sentences, front-loaded with the action and followed by the critical constraint. Every clause 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?
With annotations covering the safety profile and no output schema, the description supplies the two non-obvious facts an agent needs (windowed-only, re-pauses after one frame). Missing coverage of the not-paused or invalid-session cases keeps it from being fully complete.
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 coverage is 100% and the session_id description already explains it is 'Required only when several games run.' The description adds nothing about session_id, so the baseline 3 applies.
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 precise verb and effect ('Advance a paused game by one frame'), which is clear and actionable. It does not, however, differentiate itself from nearby siblings such as debug_step_over or debug_continue, so an agent must infer the frame-vs-debugger distinction on its own.
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?
The 'Windowed sessions only' clause is an explicit precondition/exclusion, and 'Godot re-pauses after the next drawn frame' tells the agent what happens after invocation. It stops short of naming alternatives (e.g. runtime_pause, debug_step_over) for the headless case.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.