Skip to main content
Glama
Godot MCP Server

Godot MCP Server

by neondeex

apply_theme_to_node

Assigns a Theme resource to a Control node so its styling updates automatically. Provide the node path and theme resource path to apply consistent UI theming.

Instructions

Apply a Theme resource to a Control node.

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": {
      "node_path": "<node_path>",
      "theme_path": "<theme_path>"
    },
    "name": "apply_theme_to_node"
  }
}

Input Schema

NameRequiredDescriptionDefault
node_pathYesNode path of the Control
theme_pathYesres:// path to the theme

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 behavioral disclosure but says nothing about whether an existing theme on the node is overwritten, whether the theme resource must already exist at theme_path, whether this affects editor state or is undoable, or what happens if node_path is not a Control. 'Apply' implies mutation but none of the consequences are described.

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 that states the action and the target with no wasted words. It is efficient, though the brevity leaves behavioral questions unanswered rather than being a stylistic flaw.

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

Completeness3/5

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

For a simple two-parameter tool with a fully described schema and no output schema, the description is minimally adequate: an agent knows what to pass. However, as an unannotated mutation tool it omits overwrite semantics and validation behavior, which an agent would want before invoking it.

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 node_path and theme_path documented in the schema itself. The description adds no meaning beyond those fields (no path format hints, no existence constraints), so the baseline of 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?

The description gives a specific verb and resource ('Apply a Theme resource') plus a target ('a Control node'), which is enough to distinguish it from sibling mutation tools like create_theme or set_theme_color. It stops short of an explicit contrast with those siblings, so it is clear but not maximally differentiated.

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 stated when-to-use guidance, no prerequisites (e.g., the node must exist and be a Control), and no mention of alternatives such as set_theme_color for editing an existing theme. Usage is only inferable from the verb and the parameter names.

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