Skip to main content
Glama
Godot MCP Server

Godot MCP Server

by neondeex

set_editor_setting

Set a Godot EditorSettings key to a new value through the Godot MCP Server, enabling AI-driven game development commands to adjust editor configuration.

Instructions

Set 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>",
      "value": "<value>"
    },
    "name": "set_editor_setting"
  }
}

Input Schema

NameRequiredDescriptionDefault
valueYesNew value
settingYesSetting key

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.1/5.0
Behavior1/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 discloses nothing: not whether the value is persisted across sessions, whether it takes effect immediately, whether type coercion happens, or what occurs with an unknown key or invalid value. Only the bare verb 'Set' signals mutation.

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, so it is concise, but the brevity comes at the cost of substance rather than efficiency. There is no structure beyond a single clause.

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?

For a simple two-parameter mutation tool with no annotations and no output schema, the description is still insufficient: it never explains what constitutes a valid setting key or value type (enums: 0), nor what a successful or failed call returns. The structured fields do not compensate for this gap.

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 description coverage is 100% ('Setting key', 'New value'), so the schema already documents both parameters. The description adds no syntax, type, or format meaning beyond that, which is the baseline expectation when the schema does the heavy lifting.

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

Purpose2/5

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

The description restates the tool name almost verbatim: 'Set an EditorSettings value' adds only the resource noun already present in 'set_editor_setting'. It does not differentiate this from sibling setters such as set_project_setting, nor clarify what an 'EditorSettings value' concretely is (a persisted editor preference vs. a runtime state).

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 when to prefer it over set_project_setting, and no note about prerequisites (e.g., whether the setting key must already exist). The agent must infer usage purely from the name.

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