Executes an approved project command to check Godot scenes and runtime state, ensuring only allowlisted tests run during development.
Run a command from the explicit project allowlist.
| Name | Required | Description | Default |
|---|---|---|---|
| name | Yes | ||
| timeout | No |
Changes observed during successful MCP inspections.
v0.2.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries the full burden and does disclose one important behavioral trait: execution is restricted to an explicit project allowlist. However, it says nothing about what happens for non-allowlisted commands, whether execution is mutating or destructive, how output/exit status is returned, or how timeouts affect the run.
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?
The definition is a single front-loaded sentence with no filler. It is concise to the point of under-specification, but the sentence itself 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 a command-execution tool with no annotations, no output schema, and no parameter descriptions, the definition is missing the behavioral and parameter detail an agent needs to call it safely and correctly.
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 0%, so the description must compensate. It only loosely implies that 'name' is an allowlisted command key, and it says nothing about the 'timeout' parameter, its units, or its 1–900 range.
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?
The description names a specific action and constrained resource: running a command drawn from the project's explicit allowlist. It distinguishes itself from the sibling tools, which are all inspection/validation utilities, by being the only command executor. It stops short of clarifying what 'name' identifies or who owns the allowlist.
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?
There is no guidance on when to use this tool versus the many inspection siblings, nor on preconditions such as how the allowlist is configured. The only implied rule is that the command must already be allowlisted, which is a constraint rather than usage guidance.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.