Godot Agent Loop

Overview Schema Related Servers Score Discussions

Run Project Tests

run_project_tests

Discover or run native, GUT, and GdUnit4 tests in a Godot project, returning results and optional report artifacts to verify game behavior.

Instructions

Discover or run native, GUT, and GdU…

Input Schema

TableJSON Schema

Name	Required	Description
`action`	Yes	Discover tests or run them
`failFast`	No	Stop native execution after the firs…
`framework`	No	Test framework.
`testPaths`	No	Project-relative test files or direc…
`projectPath`	Yes	Godot project path
`artifactPaths`	No	Project-relative report files to ret…
`timeoutSeconds`	No	Per-run timeout.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`ok`	Yes
`data`	No
`meta`	Yes
`error`	No

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

Addedv1.1.5Jul 26, 2026
Removedv1.1.4Jul 22, 2026

Changed9 schema fields changedv1.1.2Jul 17, 2026

addedInput schema / $schema

Added value: +"https://json-schema.org/draft/2020-12/schema"

addedInput schema / additionalProperties
```
Added value: +false
```

addedInput schema / oneOf

Added value: +[
+  {
+    "additionalProperties": true,
+    "description": "Allowed option 1",
+    "properties": {
+      "action": {
+        "const": "discover"
+      },
+      "artifactPaths": {
+        "not": {}
+      },
+      "failFast": {
+        "not": {}
+      },
+      "timeoutSeconds": {
+        "not": {}
+      }
+    },
+    "required": [
+      "action"
+    ],
+    "type": "object"
+  },
+  {
+    "additionalProperties": true,
+    "description": "Allowed option 2",
+    "properties": {
+      "action": {
+        "const": "run"
+      }
+    },
+    "required": [
+      "action"
+    ],
+    "type": "object"
+  }
+]

changedInput schema / properties / artifactPaths / description

Previous value: -"Project-relative report files to return as artifact metadata"New value: +"Project-relative report files to ret…"

changedInput schema / properties / failFast / description

Previous value: -"Stop native execution after the first failed file. Default: false"New value: +"Stop native execution after the firs…"

changedInput schema / properties / framework / description

Previous value: -"Test framework. Default: auto"New value: +"Test framework."

changedInput schema / properties / testPaths / description

Previous value: -"Project-relative test files or directories"New value: +"Project-relative test files or direc…"

changedInput schema / properties / timeoutSeconds / description

Previous value: -"Per-run timeout. Default: 60"New value: +"Per-run timeout."

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "additionalProperties": false,
+  "oneOf": [
+    {
+      "not": {
+        "required": [
+          "error"
+        ]
+      },
+      "properties": {
+        "ok": {
+          "const": true
+        }
+      },
+      "required": [
+        "data"
+      ]
+    },
+    {
+      "not": {
+        "required": [
+          "data"
+        ]
+      },
+      "properties": {
+        "ok": {
+          "const": false
+        }
+      },
+      "required": [
+        "error"
+      ]
+    }
+  ],
+  "properties": {
+    "data": {},
+    "error": {
+      "type": "object"
+    },
+    "meta": {
+      "type": "object"
+    },
+    "ok": {
+      "type": "boolean"
+    }
+  },
+  "required": [
+    "ok",
+    "meta"
+  ],
+  "type": "object"
+}

First observedv1.0.0Jul 14, 2026

TDQS

C2.4/5.0

Behavior2/5

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

Annotations are all false (no hints), and the description does not disclose behavioral traits like whether tests are run locally, if files are modified, or if a project must be open. No additional context beyond the schema.

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

Conciseness2/5

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

The description is a single truncated sentence ending with an ellipsis, under-specified and not well-structured. It fails to concisely convey the tool's function despite the schema detail.

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

Completeness2/5

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

Given the complex oneOf schema, 7 parameters, and presence of output schema, the description is severely incomplete. It does not explain the distinction between discover and run, frameworks, or return values. The schema compensates partially but the narrative is lacking.

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 the schema already documents parameter meanings. The description adds no extra semantic value beyond restating the action parameter. Baseline of 3 is appropriate.

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

Purpose3/5

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

The description states 'Discover or run native, GUT, and GdU…' indicating test operations, but it is truncated and lacks specificity. Without sibling context, the purpose is vague; however, the title 'Run Project Tests' helps. Score 3 as it gives basic verb+resource but with ambiguity.

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?

No guidelines on when to use this tool versus siblings like run_project or verify_project. No context on prerequisites or scenarios. The description does not address alternatives or when not to use.

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

Latest Blog Posts

Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)
By Om-Shree-0709 on July 25, 2026.
mcp
Agent Identity
OAuth 2.1
Your AI Chatbot Just Exposed Your CEO's Salary to an Intern
By Om-Shree-0709 on July 2, 2026.
Agent Identity
MCP Security
OAuth Delegation
Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)
By Om-Shree-0709 on June 30, 2026.
Agentic Ai
Prompt Injection
WebAssembly

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/beremaran/godot-agent-loop'

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