Skip to main content
Glama
Godot MCP Server

Godot MCP Server

by neondeex

set_theme_color

Sets a named color for a control class in a Godot Theme resource using its path and hex value, enabling targeted theme color updates.

Instructions

Set a color entry in a Theme resource.

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": {
      "theme_path": "<theme_path>",
      "node_type": "<node_type>",
      "name": "<name>",
      "color": "<color>"
    },
    "name": "set_theme_color"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesColor entry name (e.g. font_color)
colorYesColor as hex string (#rrggbb or #rrggbbaa)
node_typeYesControl class (e.g. Button, Label)
theme_pathYesres:// path to the theme

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.8/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 burden. 'Set' implies a mutation, but the description does not say whether this overwrites an existing entry, creates the entry if absent, whether the theme file is written to disk, or whether the theme must already be loaded. For a write tool with zero annotation coverage this is a significant gap.

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?

A single clean sentence with no wasted words and the verb-resource pair front-loaded. However, it is terse to the point of under-specification rather than efficiently concise.

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 four-required-parameter mutation with no annotations and no output schema, the description should at least state whether the write is persistent and what happens on conflict or missing theme. None of that is present, leaving the agent to guess at the operation's side effects.

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% and each parameter already documents its format and an example (hex string, control class, res:// path). The description adds no additional meaning beyond the schema, so the baseline 3 applies.

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 and resource ('Set a color entry in a Theme resource'), which is enough to distinguish it from siblings like set_theme_font_size and set_theme_stylebox by the target property type. It stops short of naming those siblings or explaining how the color entry relates to the rest of the theme.

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 prerequisites (e.g. must the theme already exist and be saved?), and no mention of alternatives such as set_theme_font_size or apply_theme_to_node. The agent must infer the usage context entirely from the tool 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