Skip to main content
Glama

set_project_setting

Idempotent

Edit a single project.godot setting without launching Godot. Writes one section/key value or literal in place, preserving all other lines, and returns the read-back value.

Instructions

Set one project.godot setting without launching Godot. Pass value (JSON, converted to a Godot literal) or literal (raw Godot text, e.g. "Vector2i(1280, 720)"), not both. Rewrites the last assignment in place or adds key/section; other lines stay byte for byte. Refuses autoload/* (use the autoload tools). Returns: { section, key, value read back, created, sectionCreated, previous? }.

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": {
      "projectPath": "<projectPath>",
      "section": "<section>",
      "key": "<key>"
    },
    "name": "set_project_setting"
  }
}

Input Schema

NameRequiredDescriptionDefault
keyYesSetting key within the section, e.g. "window/size/viewport_width". Same character set as section.
valueNoJSON value converted to a Godot literal: a string is quoted, an integer-valued number is an int (write 2 as literal "2.0" for a float), a boolean is true/false, an array becomes [a, b], an object a dictionary. null is not accepted; use literal "null".
literalNoRaw Godot literal written as is, on one line, with no trailing comment: "str", 1.5, true, null, [1, 2], {"a": 1} or a constructor such as Vector2i(1, 2) or PackedStringArray("a"). Checked by reading it back as one complete value. Resource(...), Object(...), ExtResource(...) and SubResource(...) are refused: Godot may then fail to load project.godot.
sectionYesINI section, e.g. "display" or "application". Letters, digits and _ . - /, no spaces.
projectPathYesPath to the Godot project directory

Output Schema

NameRequiredDescriptionDefault
keyYes
valueYesThe setting as get_project_settings reads it back after the write: a string unescaped, a number or boolean typed, anything else its raw text.
createdYesTrue when the key was added, false when an existing assignment was rewritten.
sectionYes
previousNoThe value that was replaced; absent when created.
warningsNoPresent only when there is something to say, e.g. project.godot has lines not in the form Godot writes.
sectionCreatedYesTrue when the section did not exist and was appended.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv4.0.1

TDQS

A4.3/5.0
Behavior3/5

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

Adds substantial behavior beyond idempotentHint=true: byte-for-byte preservation of untouched lines, in-place rewrite of the last assignment, section creation flags, and refusal of Resource/Object/ExtResource literals with a stated rationale. It is consistent with the annotations, but per the scoring rule with annotations already covering the safety profile and a full output schema present, this lands at a solid 3 rather than higher.

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?

Four dense sentences, each carrying distinct information — purpose, parameter contract, write mechanics, refusal, return shape — with the core purpose front-loaded and zero filler.

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?

An output schema exists, yet the description still names the returned fields and flags the optional 'previous', covering rollback awareness. Combined with the refusal rules and write semantics, nothing an agent needs before calling 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?

Schema coverage is 100%, so baseline is 3, but the description adds a genuinely non-schema rule: 'Pass value ... or literal ..., not both.' That mutual exclusivity, plus the 'Godot may then fail to load project.godot' consequence, is meaning the schema does not convey.

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?

States a specific verb and resource ('Set one project.godot setting') plus a scope constraint ('without launching Godot') that separates it from launch_editor and the node/resource setters. The autoload/* exclusion further pins down its domain.

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?

Gives an explicit when-not ('Refuses autoload/* (use the autoload tools)') and clarifies the value-vs-literal choice. It does not point to a reading counterpart (e.g. get_project_settings) for verifying or listing existing settings, so guidance stops just short of full routing.

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