Skip to main content
Glama
Sign In
Godot MCP Bridge

Godot MCP Bridge

by farrasfadhils
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Local

set_theme_stylebox

Set theme stylebox overrides in Godot projects to customize UI element appearances programmatically through the MCP Bridge.

Instructions

Set theme stylebox override. (Compatibility tool)

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "set_theme_stylebox"
  }
}

Input Schema

NameRequiredDescriptionDefault
timeoutMsNo
autoConnectNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

D1.9/5.0
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations provided, the description carries the full disclosure burden. It offers only the minimal hint that this is a 'Compatibility tool' without explaining mutation scope, persistence, side effects on the theme resource, or the connection mechanism implied by the parameter names.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

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

While brief (two fragments), the description is under-specified rather than efficiently concise. Given the complete lack of schema documentation and annotations, the brevity represents an information gap rather than effective communication.

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?

Inadequate for a tool with undocumented parameters and no output schema. The description fails to explain the Godot editor connection context (evident from sibling tools like godot_connect), the role of timeoutMs/autoConnect, or the implications of setting a stylebox override.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, yet the description fails to explain either parameter. The parameter names (timeoutMs, autoConnect) suggest connection-oriented behavior inconsistent with the theme-styling stated purpose, creating confusion that the description does not resolve.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states the core action ('Set theme stylebox override') with a specific verb and resource type, distinguishing it from siblings like set_theme_color or set_theme_font_size. However, the parenthetical '(Compatibility tool)' is unexplained jargon that obscures when to use this, and 'override' lacks context for agents unfamiliar with Godot theme systems.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines1/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance provided on when to use this tool versus create_theme or other set_theme_* siblings. The 'Compatibility tool' label hints at specific use cases but offers no explicit criteria for selection or prerequisites.

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