Skip to main content
Glama
Godot MCP Server

Godot MCP Server

by neondeex

get_theme_colors

Fetches all color entries from a Godot Theme resource using its res:// path, helping you inspect and reuse theme colors in AI-driven game development.

Instructions

Get all color entries 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>"
    },
    "name": "get_theme_colors"
  }
}

Input Schema

NameRequiredDescriptionDefault
theme_pathYesres:// path to the theme

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.2/5.0
Behavior3/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. It does signal a non-mutating bulk read ('all color entries'), which usefully implies no filtering or pagination, but it says nothing about failure behavior for a bad theme_path, caching, or whether nested/inherited theme colors are included.

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?

One short sentence with the verb and scope front-loaded and no wasted wording. It is efficient, though arguably so terse that it borders on under-specification rather than optimal concision.

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 one-parameter read tool this is close to adequate, but with no output schema the description never explains what a 'color entry' contains (name-to-color mapping, type variants), which is the main thing an agent needs before consuming the result.

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?

The single parameter theme_path is fully documented in the schema as a 'res:// path to the theme', so schema coverage is 100% and the baseline applies. The description adds no format hints, path resolution notes, or error semantics beyond the schema.

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 and resource ('Get all color entries in a Theme resource'), which is clearly a read of color entries rather than fonts or styleboxes, distinguishing it from siblings like set_theme_color and set_theme_font_size. It does not explicitly contrast with get_theme_info, so sibling differentiation is only partial.

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 explicit when-to-use guidance, no prerequisites, and no named alternative. The agent must infer that this is the read counterpart to set_theme_color and that get_theme_info covers broader theme metadata; nothing in the text says so.

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