Skip to main content
Glama

validate_project

Checks every script for parse errors and runs a Godot project headless to catch scene and load errors, returning ok: true only when no errors are reported.

Instructions

Check every script for parse errors and run the project headless to catch scene and load errors. Returns ok: true only when Godot reports no 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": {
      "project": "<project>"
    },
    "name": "validate_project"
  }
}

Input Schema

NameRequiredDescriptionDefault
projectYesProject folder name under the projects directory

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior3/5

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

With no annotations, the description carries the load and does disclose two useful traits: the check runs headless and the success signal is ok:true only on a clean Godot report. It omits other behaviorally relevant facts for a no-annotation tool: whether the headless run writes or modifies project files, roughly how long it takes, and how failures are surfaced (error list? message?).

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?

Two tight sentences with no filler, and the core behavior (parse check + headless run) is front-loaded before the return-value note. Every clause earns its place.

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

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a one-parameter tool with no output schema, the description covers what it does and the shape of the success result. The remaining gap is failure reporting detail — an agent knows what ok:true means but not what accompanies ok:false.

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?

There is a single parameter with 100% schema description coverage ('Project folder name under the projects directory'), so the schema already explains it. The description adds nothing about the project parameter, which is acceptable but not additive; baseline 3 applies.

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

Purpose5/5

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

Names a specific operation on a specific resource: parsing every script and running the project headless to catch scene/load errors. That is clearly a validation action, which distinguishes it from the create_/add_/set_ siblings that build projects rather than check them.

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 implied rather than stated: the agent can infer this is a post-change sanity check because it 'catches scene and load errors.' There is no explicit when-to-use trigger, no prerequisites (e.g., must the project exist first, does Godot need to be installed), and no statement about when this is unnecessary or what to do instead.

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