Skip to main content
Glama
Godot MCP Server

Godot MCP Server

by neondeex

get_editor_setting

Retrieves a specific Godot EditorSettings value by key so AI-driven workflows can inspect editor configuration and adapt commands accordingly.

Instructions

Get an EditorSettings value.

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": {
      "setting": "<setting>"
    },
    "name": "get_editor_setting"
  }
}

Input Schema

NameRequiredDescriptionDefault
settingYesSetting key

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.5/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden, yet it says nothing about what happens when the key does not exist, whether defaults are returned, or what type the value has. For a getter with no output schema, that is a meaningful gap even if the operation is low-risk.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

One short sentence with no wasted words and the key idea front-loaded, but it is under-specified rather than tight: the terseness comes at the cost of missing detail rather than from efficient editing.

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

Completeness2/5

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

The tool is simple (one required parameter, no nesting), but with no output schema and no annotations, the description should at minimum say what a returned value looks like or how missing keys behave. As written, an agent cannot predict the response shape.

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?

Schema coverage is 100%, and the single "setting" parameter is described as "Setting key", so the schema already does the work. The description adds no format hints or examples of valid keys, which is consistent with a baseline 3.

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

Purpose3/5

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

States a verb ("Get") and a resource ("EditorSettings value"), which is slightly more specific than the name alone because it names the Godot EditorSettings class. However, it does not distinguish this from the sibling get_project_setting, nor does it clarify what a "value" can be.

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

Usage Guidelines2/5

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

There is no when-to-use guidance, no mention of the paired sibling set_editor_setting, and no hint about when to prefer get_editor_setting over get_project_setting. The agent must infer the editor-vs-project distinction from names alone.

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