Skip to main content
Glama
Sign In
godot-forge

godot-forge

by gregario
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

godot_get_diagnostics

Read-onlyIdempotent

Retrieve code errors and warnings from Godot's language server diagnostics. Specify a file path or omit for project-wide analysis.

Instructions

Get LSP diagnostics (errors, warnings) from Godot's built-in language server. Requires Godot editor to be running with the project open.

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_get_diagnostics"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathNoFile path to get diagnostics for (e.g., scripts/player.gd). Omit for project-wide.
portNoLSP port (default: 6005)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4.2/5.0
Behavior4/5

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

Annotations indicate read-only and idempotent. Description adds the runtime requirement of having the editor open and project loaded, which is beyond annotation scope. No contradictions.

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 concise sentences, no unnecessary words. Front-loaded with the core action and critical requirement.

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?

Describes what the tool does and a key prerequisite. Lacks explanation of return value format (e.g., list of diagnostics), but given the name and context, it is reasonably complete.

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?

Input schema has 100% coverage with good descriptions. Description does not add extra meaning beyond schema; it mentions 'errors, warnings' but not parameter-specific. Baseline 3 is appropriate.

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?

Description clearly states verb 'get', resource 'LSP diagnostics', and context 'from Godot's built-in language server'. It distinguishes from siblings like godot_analyze_scene by specifying diagnostics retrieval.

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

Usage Guidelines4/5

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

Provides a critical prerequisite ('Requires Godot editor to be running with the project open'), giving clear when-to-use guidance. Does not explicitly compare to alternatives, but the prerequisite is essential and well-stated.

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