Skip to main content
Glama
Beckett — MCP for Godot

Beckett — MCP for Godot

by beckettlab

set_project_setting

Destructive

Sets a Godot ProjectSettings value, writes it to project.godot, and preserves or validates typed values so incompatible input is refused.

Instructions

Set a ProjectSettings value and persist project.godot. The property path goes in 'setting' ('name' is also accepted); e.g. set application/run/main_scene to res://main.tscn. A setting that already holds a typed value keeps its type: colors take "#rrggbb" or [r,g,b,a], vectors [x,y]. A value that cannot convert is refused, not stored.

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": {
      "value": "<value>"
    },
    "name": "set_project_setting"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNo
valueYes
settingNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.12.1
  2. Removedv1.10.0
  3. First observedv1.0.0

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare destructive=true and readOnly=false, and the description adds meaningful behavior: it persists project.godot, preserves typed values, and refuses values that cannot convert. The remaining gap is that it does not explain the scope or reversibility of the destructive write.

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?

The description is four tight sentences, front-loads the core action, and every sentence adds useful detail about aliasing, examples, or type conversion.

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

Completeness4/5

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

For a three-parameter destructive mutation with no output schema, the description covers the target file, path alias, example usage, and conversion behavior. It is nearly complete, missing only explicit success/return details that an output schema would normally provide.

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 0%, so the description must compensate, and it does explain that 'setting' is the property path while 'name' is accepted as an alias. It also documents value formats for colors and vectors and states that incompatible values are rejected, though it does not fully enumerate all supported value types.

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 gives a specific verb and resource: 'Set a ProjectSettings value and persist project.godot.' This clearly distinguishes the tool from sibling readers like get_project_setting and from generic property setters.

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

Usage Guidelines3/5

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

The example implies the tool is for editing project configuration, but the description never explicitly names alternatives such as set_property or get_project_setting, nor does it state when not to use this tool.

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