Skip to main content
Glama
Godot MCP Server

Godot MCP Server

by neondeex

set_project_setting

Set a Godot ProjectSettings value by key to configure project behavior directly from Claude Code via MCP.

Instructions

Set a project setting value in the Godot ProjectSettings.

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

Input Schema

NameRequiredDescriptionDefault
valueYesNew value for the setting
settingYesSetting key (e.g. application/config/name)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.9/5.0
Behavior2/5

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

With no annotations, the description carries the full burden of disclosure and does not meet it. It does not say whether the setting key must already exist, whether the change persists to project.godot on disk, whether an open editor is required, or what error behavior looks like for an invalid key — all critical for a mutation tool.

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

Conciseness4/5

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

A single front-loaded sentence with no wasted words. It is efficient, though its brevity contributes to the gaps noted in other dimensions rather than being a structural flaw.

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 state-mutating tool with zero annotation coverage and no output schema, this is under-specified. Persistence behavior, required editor state, failure modes, and the relationship to get_project_setting / set_editor_setting are all left unaddressed.

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%, with both `setting` (including an example key format) and `value` documented in the schema, so the baseline of 3 applies. The description adds only the ProjectSettings domain context, no format, type, or validation semantics beyond the schema.

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?

States a specific verb ("Set") and resource ("a project setting value in the Godot ProjectSettings"), which distinguishes it from editor-level siblings such as set_editor_setting. It never explicitly names or contrasts those siblings, so it stops short of full differentiation.

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 prerequisites, and no pointer to the obvious alternatives (set_editor_setting for editor settings, get_project_setting for reads). The agent must infer the project vs. editor scope distinction from the word "project" 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