Skip to main content
Glama
Godot MCP Server

Godot MCP Server

by neondeex

set_theme_stylebox

Sets a StyleBox entry in a Godot Theme resource to define or override control styles by node type, state name, and StyleBox type.

Instructions

Set a StyleBox 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>",
      "stylebox_type": "<stylebox_type>"
    },
    "name": "set_theme_stylebox"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesStyleBox entry name (e.g. normal, hover)
node_typeYesControl class
propertiesNoStyleBox property overrides
theme_pathYesres:// path to the theme
stylebox_typeYesStyleBox class (StyleBoxFlat, StyleBoxTexture, etc.)

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?

No annotations are provided, so the description carries the full behavioral burden. It does not state whether this creates or overwrites an entry, how 'properties' overrides are merged, whether the theme must already exist, or what happens on failure.

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?

The description is a single front-loaded sentence with no filler. It is efficient, but arguably too terse for a five-parameter nested mutation tool.

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 mutation with a nested 'properties' object, no annotations, and no output schema, the description omits key context about overwrite semantics, required theme state, and the effect of property overrides. The complete schema helps with parameters but does not fill the behavioral 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%, so the schema already documents all five parameters. The description adds no meaning beyond that, such as how stylebox_type interacts with node_type or how properties overrides are applied.

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?

The description states a specific verb, 'Set', and a specific resource, 'StyleBox entry in a Theme resource'. It distinguishes itself from siblings like set_theme_color and set_theme_font_size by naming StyleBox, but it does not explicitly clarify scope or differentiate usage.

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, when-not-to-use, or alternative guidance. It implies this is the tool for setting a theme StyleBox, but leaves unclear when to prefer it over batch_set_property, apply_theme_to_node, or create_theme.

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