Skip to main content
Glama
Sign In
Godot MCP Bridge

Godot MCP Bridge

by farrasfadhils
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Local

validate_script

Validate Godot script syntax to detect coding errors. Analyzes code structure and identifies compilation issues in Godot Engine projects via MCP Bridge.

Instructions

Validate script syntax. (Compatibility tool)

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "validate_script"
  }
}

Input Schema

NameRequiredDescriptionDefault
timeoutMsNo
autoConnectNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.4/5.0
Behavior2/5

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

With no annotations provided, the description carries full disclosure burden but omits critical behavioral details: whether validation results are returned or thrown as errors, what 'autoConnect' connects to, the purpose of 'timeoutMs', and what constitutes a validation failure versus success.

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

Conciseness3/5

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

Extremely concise (4 words), but this brevity constitutes under-specification rather than efficiency. The parenthetical '(Compatibility tool)' consumes space without providing actionable context. Front-loaded structure is good, but content is insufficient for the complexity.

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?

Incomplete given zero schema annotations, 0% parameter coverage, no output schema, and ambiguous 'compatibility' designation. For a validation tool, the description should indicate return format (boolean/error list) and whether it performs side effects, but provides none of this context.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% and the description adds no meaning to either parameter. 'timeoutMs' and 'autoConnect' are undocumented—description fails to explain what timeout applies to (validation duration?) or what connection 'autoConnect' establishes, nor does it mention 'additionalProperties: true' flexibility.

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 states a clear action ('Validate') and target ('script syntax'), distinguishing it from sibling tools like 'execute_script' or 'create_script'. However, the parenthetical '(Compatibility tool)' is ambiguous and doesn't clarify scope versus alternatives like 'edit_script'.

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 explicit guidance on when to use this versus 'edit_script' or 'read_script'. The '(Compatibility tool)' notation hints at specific context but fails to explain what compatibility concerns warrant using this tool over 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