Skip to main content
Glama
Godot MCP Server

Godot MCP Server

by neondeex

assert_node_state

Verify that a running game node's properties match expected values to catch state mismatches during Godot testing.

Instructions

Assert that a node's properties match expected values in the running game.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "node_path": "<node_path>",
      "assertions": "<assertions>"
    },
    "name": "assert_node_state"
  }
}

Input Schema

NameRequiredDescriptionDefault
node_pathYesNode path in the running game
assertionsYesProperty→expected-value pairs to assert

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.1/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full disclosure burden. It hints that a game must be running, but for an assertion tool the critical behavior is what happens on failure (raise an error, return a boolean, abort the test) and that is entirely absent, as is any mention of return values.

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

Conciseness4/5

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

A single well-formed sentence with the scope constraint front-loaded and no filler. It is efficient, though its brevity is partly the source of the disclosure gaps rather than a virtue on its own.

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?

For a two-parameter assertion tool with a nested assertions object, no output schema, and no annotations, the definition should say what a passing and failing assertion look like. Neither is covered, leaving the agent unable to interpret the result of the call.

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% with both parameters documented, so the baseline is 3. The description reinforces that assertions are property→expected-value pairs and that node_path targets the running game, but adds no syntax or format detail beyond the schema.

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

Purpose4/5

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

States a specific verb (assert) and resource (node properties) plus the scope 'in the running game', which distinguishes it from read-only siblings like get_game_node_properties and get_editor_state. It does not name any sibling explicitly, so differentiation rests on the verb alone.

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

Usage Guidelines3/5

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

The 'in the running game' clause implies this is a verification step against a live game rather than editor state, which is a useful usage cue. However, it never says when to prefer this over get_game_node_properties plus manual comparison, nor does it state any preconditions or alternatives.

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

Deploy Server

Other Tools