Gear

Overview Schema Source Related Servers Discussions Admin

editor-version

Returns the installed Godot engine version for compatibility checks, e.g., verifying Godot 4.4+ features like UID.

Instructions

[compact alias of get_godot_version] Returns the installed Godot engine version string. Use to check compatibility (e.g., Godot 4.4+ features like UID). Returns version like "4.3.stable" or "4.4.dev".

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": {
      "reason": "<reason>"
    },
    "name": "editor-version"
  }
}

Input Schema

Name	Required	Description	Default
`reason`	Yes	Brief explanation of why you are calling this tool

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.1May 7, 2026

TDQS

A4.1/5.0

Behavior3/5

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

No annotations are provided, so the description bears full burden. It states the tool returns a version string and implies no side effects, but does not explicitly confirm read-only behavior or mention any potential limitations like rate limits. Adequate but not thorough.

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 sentences, each line earns its place: first sentence states the core function, second provides usage guidance and return format. No unnecessary words.

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?

Given the tool's simplicity (one parameter, no output schema, no annotations), the description fully covers what a user needs: what it returns, why to use it, and example outputs. No gaps.

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?

The input schema has 100% coverage with a single 'reason' parameter described as 'Brief explanation of why you are calling this tool'. The description adds no additional semantics for the parameter beyond what the schema provides, baseline score of 3.

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?

The description clearly states the tool returns the installed Godot engine version string, giving example return formats like '4.3.stable' or '4.4.dev'. It uniquely identifies itself as an alias of get_godot_version, distinguishing it from sibling tools.

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?

The description explicitly says 'Use to check compatibility (e.g., Godot 4.4+ features like UID)', providing a clear use case. While it doesn't mention when not to use, the context is sufficient for a simple read-only tool.

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