Skip to main content
Glama
Godot MCP Server

Godot MCP Server

by neondeex

create_theme

Creates a new Theme resource file at a specified res:// path so you can define custom UI styling for Godot scenes and controls.

Instructions

Create a new Theme resource file.

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": {
      "path": "<path>"
    },
    "name": "create_theme"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathYesres:// path for the theme file

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 and says nothing about what happens if the path already exists, whether the file is overwritten, what permissions or project context are required, or what the return value is. For a filesystem-writing tool 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.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single front-loaded sentence with no filler; the main weakness is under-specification rather than verbosity, which is penalized elsewhere.

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?

The tool is simple (one required, fully documented parameter, no output schema), so the description is arguably enough to call it. It still omits the one behavior an agent most needs, namely what happens on path collision.

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 path parameter ("res:// path for the theme file") is already documented. The description adds no further meaning such as whether directories must exist or whether the extension is implied.

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?

"Create a new Theme resource file" gives a specific verb (create) plus resource type (Theme resource file), so the agent knows exactly what is produced. It does not differentiate from sibling creation tools such as create_resource or create_scene, which is the only deduction.

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 statement of when to prefer this over create_resource or when a Theme is appropriate. No prerequisites, no follow-up guidance (e.g., that apply_theme_to_node or set_theme_color are used afterward).

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