Skip to main content
Glama
Godot MCP Server

Godot MCP Server

by neondeex

assert_screen_text

Verify that specified text appears on screen within a timeout, failing the check if it does not, to validate Godot UI or game state during automated tests.

Instructions

Assert that a given text string appears on the screen within a timeout.

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": {
      "text": "<text>"
    },
    "name": "assert_screen_text"
  }
}

Input Schema

NameRequiredDescriptionDefault
textYesText to look for on screen
timeoutNoSeconds to wait before failing (default: 5.0)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.3/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full burden. It does disclose one valuable behavioral trait: the tool blocks/polls until a timeout elapses before failing, which tells the agent this call may take up to the timeout duration. It does not say what failure looks like (raised error vs. returned false), nor what is returned on success.

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?

A single front-loaded sentence with zero filler; the assertion target and the timing condition are both stated immediately.

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

Completeness3/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 no annotations and no output schema, the description should say what a failed assertion returns or raises and whether success yields any value. It covers the waiting behavior but leaves the result contract unstated.

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%, with both 'text' and 'timeout' documented including the 5.0 default, so the schema already does the heavy lifting. The description adds nothing beyond restating the existence of a text string and a timeout, so the baseline 3 applies.

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 and resource ('Assert that a given text string appears on the screen') plus a timing condition, which is enough to distinguish it from mutation-oriented siblings. It does not differentiate itself from the sibling assert_node_state, which covers a related but different assertion target.

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?

The description gives no when-to-use context, no prerequisites (e.g. that a screen/frame capture is required), and no guidance on when to prefer this over assert_node_state or other verification tools. Usage is only implied by the word 'Assert'.

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