Skip to main content
Glama

AAA review

godot_review

Statically reviews Godot projects without launching the engine to catch incorrect APIs, performance issues, and code-quality problems, returning category scores and file-level findings with fixes.

Instructions

Static AAA review of the project, no Godot needed: API correctness (Godot 3 code, unknown classes, members and signals, wrong argument counts, missing input actions), performance, code quality and structure. Returns a 0-100 score per category, then one line per finding, res://file.gd:12: error [rule] message, and the same as JSON (structuredContent); detail full adds each fix. files lists only findings in files you changed. code + file reviews GDScript before you write it. only_new: true while fixing: new findings in full, ones you saw as one short line, and how many are fixed. An older 4.x project also gets what changes on the way to 4.7; from/target set that range. It never changes your code (it keeps the last review in .godot/godotwright/ for only_new and counts rule hits in the local learning file). For errors only the engine finds, run godot_check; godot_checklist lists every rule.

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": "godot_review"
  }
}

Input Schema

NameRequiredDescriptionDefault
codeNounsaved GDScript to review in place of the file on disk
fileNores:// path the code belongs to (required with code)
fromNorelease it comes from (default: the version saved in project.godot)
pathNoproject folder, or a file or folder inside it (relative to the server's folder; default: the current project)
filesNoonly show findings in these res:// files
detailNobrief (capped lists) or full (everything); default full
targetNoGodot release the project moves to, "4.1" to "4.7" (default 4.7)
only_newNoshow only what changed since the last review of this project (saves tokens in a fix loop)

Output Schema

NameRequiredDescriptionDefault
okYes
errorsYes
overallYes
projectYes
findingsYes
warningsYes
truncatedYes
categoriesYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changedv0.6.0
    • changedInput schema / properties / detail / description
      Previous value: -"brief: short output with capped lists; full: everything (default for this premium profile: full)."New value: +"brief (capped lists) or full (everything); default full"
    • addedInput schema / properties / from
      Added value: +{
      +  "description": "release it comes from (default: the version saved in project.godot)",
      +  "type": "string"
      +}
    • changedInput schema / properties / path / description
      Previous value: -"The project folder, or any file or folder inside it (Godotwright walks up to project.godot). Relative paths start at the server's folder. Default: the current project."New value: +"project folder, or a file or folder inside it (relative to the server's folder; default: the current project)"
    • addedInput schema / properties / target
      Added value: +{
      +  "description": "Godot release the project moves to, \"4.1\" to \"4.7\" (default 4.7)",
      +  "type": "string"
      +}
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "$schema": "http://json-schema.org/draft-07/schema#",
      +  "additionalProperties": false,
      +  "properties": {
      +    "categories": {
      +      "additionalProperties": {
      +        "type": "number"
      +      },
      +      "propertyNames": {
      +        "type": "string"
      +      },
      +      "type": "object"
      +    },
      +    "errors": {
      +      "type": "number"
      +    },
      +    "findings": {
      +      "items": {
      +        "additionalProperties": false,
      +        "properties": {
      +          "count": {
      +            "type": "number"
      +          },
      +          "file": {
      +            "type": "string"
      +          },
      +          "line": {
      +            "type": "number"
      +          },
      +          "message": {
      +            "type": "string"
      +          },
      +          "rule": {
      +            "type": "string"
      +          },
      +          "severity": {
      +            "enum": [
      +              "error",
      +              "warning",
      +              "info"
      +            ],
      +            "type": "string"
      +          },
      +          "source": {
      +            "type": "string"
      +          }
      +        },
      +        "required": [
      +          "severity",
      +          "message"
      +        ],
      +        "type": "object"
      +      },
      +      "type": "array"
      +    },
      +    "ok": {
      +      "type": "boolean"
      +    },
      +    "overall": {
      +      "type": "number"
      +    },
      +    "project": {
      +      "type": "string"
      +    },
      +    "truncated": {
      +      "type": "number"
      +    },
      +    "warnings": {
      +      "type": "number"
      +    }
      +  },
      +  "required": [
      +    "ok",
      +    "errors",
      +    "warnings",
      +    "findings",
      +    "truncated",
      +    "project",
      +    "overall",
      +    "categories"
      +  ],
      +  "type": "object"
      +}
  2. Changed2 schema fields changedv0.1.1
    • changedInput schema / properties / detail / description
      Previous value: -"Output detail (default for this premium profile: full)."New value: +"brief: short output with capped lists; full: everything (default for this premium profile: full)."
    • changedInput schema / properties / path / description
      Previous value: -"Project directory or a path inside it (default: the current project)."New value: +"The project folder, or any file or folder inside it (Godotwright walks up to project.godot). Relative paths start at the server's folder. Default: the current project."
  3. First observedv0.1.0

TDQS

A4.8/5.0
Behavior5/5

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

Annotations say readOnlyHint=false and idempotentHint=false, and the description explains why in useful detail: it never edits your code but does persist the last review under .godot/godotwright/ and accumulates rule-hit counts in a local learning file, so state is written and repeated calls differ. It also discloses the output shape (0-100 per category, `res://file.gd:12: error [rule] message`, plus structuredContent) and that `detail: full` adds fixes, which no annotation conveys.

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?

Front-loaded with the one-line purpose, then packed with mode-specific clauses in a logical order (output format → file filter → pre-write review → fix loop → migration → side effects → alternatives). It is dense and backtick-heavy, so the fix-loop and migration clauses require re-reading, but nearly every sentence carries information an agent needs.

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

Completeness5/5

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

With 8 optional parameters, an output schema, and file-system side effects, this is a complex tool, and the description covers the return format, persistence behavior, every distinct invocation mode, and sibling boundaries. Nothing an agent needs to call it correctly in a given situation is missing.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3; the description earns extra credit by adding workflow meaning the schema does not: `only_new` returns new findings in full plus one-line repeats and a count of what got fixed, and `from`/`target` define a migration range rather than isolated version strings. A few semantics (e.g. how `path` interacts with `files`) still rest on the schema alone, so it is not a 5.

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?

Opens with a specific verb+resource+scope: 'Static AAA review of the project, no Godot needed', then enumerates the exact rule categories checked (API correctness, performance, code quality). It explicitly contrasts itself with siblings by naming godot_check for engine-only errors and godot_checklist for the rule list, so an agent can pick it without opening another schema.

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

Usage Guidelines5/5

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

Gives concrete when-to-use routing for each mode: `files` for changed files, `code`+`file` for pre-write review of GDScript, `only_new: true` while in a fix loop, and `from`/`target` when an older 4.x project migrates. It also names the alternatives (godot_check, godot_checklist) and the condition that selects them, which is exactly what usage guidance should do.

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