Skip to main content
Glama
Godot MCP Server

Godot MCP Server

by neondeex

validate_script

Check a GDScript file for syntax and parse errors before execution. Provide a res:// path to detect issues early and keep Godot scripts working.

Instructions

Check a GDScript file for syntax/parse errors.

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": {
      "path": "<path>"
    },
    "name": "validate_script"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathYesres:// path of the script to validate

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.3/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 and does not meet it. 'Check' implies a read-only operation, but it never confirms the file is not modified, nor does it say whether errors are returned as a structured list with line numbers or merely a pass/fail.

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?

One short, front-loaded sentence with the operation and its target leading. Nothing redundant and nothing padded.

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 one-parameter static validator this is close to adequate, since the schema fully documents the input. The gap is the missing output contract: with no output schema, an agent cannot tell whether it gets error lines, messages, or a boolean, which matters for deciding whether to act on the result.

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% and the single 'path' parameter is fully documented in the schema ('res:// path of the script to validate'), so the baseline is 3. The description adds no extra meaning about path format or whether relative/dynamic paths are accepted.

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?

The description names a specific verb ('Check') and resource ('a GDScript file') and bounds the scope to 'syntax/parse errors', which separates it from execution tools like execute_game_script or analysis tools like analyze_code_complexity. It stops short of explicitly naming a sibling it is not, so it lands at 4 rather than 5.

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?

Usage is only implied: 'syntax/parse errors' signals this is a static pre-flight check rather than a runtime/behavior check. There is no explicit statement of when to call it, whether it should precede create_script/edit_script/execute_game_script, or any alternative to prefer.

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