Godot Agent Loop

Overview Schema Related Servers Score Discussions

Verify Project

verify_project

Run a Godot project and evaluate bounded assertions to verify game behavior, with options to wait frames, capture screenshots, and stop after checks.

Instructions

Run bounded assertions and capture e…

Input Schema

TableJSON Schema

Name	Required	Description
`scene`	No	Optional scene to run
`teardown`	No	Stop the project after verification.
`assertions`	No	Bounded assertions evaluated against…
`waitFrames`	No	Frames to wait before assertions.
`projectPath`	Yes	Godot project path
`captureScreenshot`	No	Capture a screenshot and return its…

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.

Changed13 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
```

changedInput schema / properties / assertions / description

Previous value: -"Bounded assertions evaluated against the running game"New value: +"Bounded assertions evaluated against…"

addedInput schema / properties / assertions / items / additionalProperties
```
Added value: +false
```
removedInput schema / properties / assertions / items / properties / count / description
```
Removed value: -"Expected group member count"
```
removedInput schema / properties / assertions / items / properties / group / description
```
Removed value: -"Group name for group_count"
```
removedInput schema / properties / assertions / items / properties / kind / description
```
Removed value: -"Assertion kind"
```
removedInput schema / properties / assertions / items / properties / nodePath / description
```
Removed value: -"Node path for node_exists"
```
removedInput schema / properties / assertions / items / properties / text / description
```
Removed value: -"Required output substring for log_contains"
```

changedInput schema / properties / captureScreenshot / description

Previous value: -"Capture a screenshot and return its SHA-256 digest. Default: false"New value: +"Capture a screenshot and return its…"

changedInput schema / properties / teardown / description

Previous value: -"Stop the project after verification. Default: true"New value: +"Stop the project after verification."

changedInput schema / properties / waitFrames / description

Previous value: -"Frames to wait before assertions. Default: 2"New value: +"Frames to wait before assertions."

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, so description must disclose behavior. The truncated description only mentions running assertions and capturing something, but does not clarify side effects, permissions, or state changes.

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, which is under-specification rather than conciseness. It fails to provide a complete, well-structured overview.

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 tool's complexity (6 parameters, assertions array) and existing output schema, the description is far too brief to inform an agent about the tool's full capabilities and usage.

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 coverage is 100%, so the baseline is 3. The description adds minimal meaning beyond the schema; it does not elaborate on parameters like assertions or teardown.

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 fragment 'Run bounded assertions and capture e…' vaguely indicates running assertions on a project, but it is incomplete and uses jargon. Among sibling tools like run_project_tests or read_scene, this tool's specific role is not clearly distinguished.

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 guidance is provided on when to use verify_project versus siblings like run_project_tests or read_scene. The description lacks any context for selection.

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