Skip to main content
Glama
robertobendi

WazziCode Godot

by robertobendi

test_run

Run GDScript test suites in the connected Godot editor. Discovers test_*.gd files, executes all test_* methods, and returns pass/fail summaries with failures highlighted.

Instructions

Run GDScript test suites inside the connected Godot editor.

Discovers test_*.gd in res://tests/, instantiates them, and runs all test_* methods. Returns a compact summary by default (counts, suite names, duration) plus failures only. verbose=True includes every individual test result (each with per-test duration_ms).

The whole run has a 300s budget; the plugin aborts between tests shortly before it expires and returns TEST_RUN_TIMEOUT with the partial summary (full partials via test_manage(op="results_get")). Long suites are safe — the editor services the MCP transport between tests — but one single test blocking the main thread for 20s+ can still drop the session. Not allowed inside batch_execute.

The response includes edited_scene (the scene currently open in the editor). Many suites assume the project's main scene is open; if it is not and there are failures, the response also carries a scene_warning — open the main scene (scene_open) and re-run before treating those failures as real.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
suiteNoRun only the named suite (e.g. "scene", "node", "editor"). Empty runs all suites.
verboseNoInclude every individual test result. Default False.
test_nameNoRun only tests whose name contains this substring.
session_idNoOptional Godot session to target. Empty = active session.
exclude_test_nameNoSkip tests whose name contains this substring.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior5/5

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

No annotations exist, so the description carries the full burden. It discloses the 300s budget, timeout return code TEST_RUN_TIMEOUT, partial summary behavior, the risk of a 20s+ single test blocking the main thread, and the scene_warning mechanism. This far exceeds minimal disclosure and gives the agent critical context about side effects and failure modes.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is structured in three paragraphs, each covering a distinct aspect: execution, timeout/safety, and response details. The first sentence immediately states purpose, and every sentence contributes unique information about behavior or constraints. The length is justified by the tool's complexity, and there is no redundant fluff.

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

Completeness5/5

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

The description covers execution model, timeout behavior, partial results, session safety, batch_execute exclusion, main scene dependency, and response content. Given that an output schema exists, the description need not enumerate fields, but it explains the essential context for correct usage, making it fully complete for an agent to select and invoke the tool correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3. The description enhances parameter understanding by explaining that verbose=True yields per-test duration_ms, which is not in the schema, and by tying the suite parameter to the discovery of test_*.gd files. It also adds context about the response containing edited_scene, which is not explicitly stated in the schema.

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

Purpose5/5

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

The description opens with a specific verb+resource: 'Run GDScript test suites inside the connected Godot editor.' It then details the discovery and execution of test_*.gd files and test_* methods, clearly distinguishing the tool from test_manage by referencing it for retrieving partial results.

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

Usage Guidelines5/5

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

The description explicitly states 'Not allowed inside batch_execute' and advises opening the main scene with scene_open when a scene_warning appears. It also points to test_manage(op="results_get") as the alternative for obtaining full partial results, providing clear when-to-use and when-not-to-use guidance.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/robertobendi/wazzicode-godot'

If you have feedback or need assistance with the MCP directory API, please join our Discord server