Skip to main content
Glama
Godot MCP Server

Godot MCP Server

by neondeex

get_project_info

Retrieve the current Godot project's name, path, engine version, and settings to understand project context before issuing editor commands.

Instructions

Get general information about the current Godot project (name, path, Godot version, settings).

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.7/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the disclosure burden. The verb 'Get' plus 'current Godot project' reasonably implies a read-only, no-side-effect operation, and the parenthetical previews what comes back. It still omits any statement about error behavior when no project is open or about the shape/size of the returned settings blob.

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?

A single front-loaded sentence with the resource and the returned fields, and no filler. 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 zero-argument read tool with no output schema, the description is close to sufficient: it names the resource and sketches the contents. A slightly better definition would clarify the relationship to the settings and statistics siblings, but nothing essential for calling it 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?

The tool takes zero parameters, so there is nothing for the description to disambiguate; the baseline for a no-parameter tool applies. The parenthetical does useful work by telling the agent which facts it can expect without a second call.

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?

Uses a specific verb (Get) plus a clearly scoped resource (general information about the current Godot project) and enumerates the payload fields: name, path, Godot version, settings. It does not, however, distinguish itself from close siblings like get_project_setting or get_project_statistics, and the word 'settings' in the field list partially overlaps the dedicated settings tool.

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: an agent can infer this is the broad orientation call for a project. There is no explicit when-to-use, no statement of when to prefer get_project_setting or get_project_statistics instead, and no prerequisites (e.g. whether an editor session must be open).

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