Skip to main content
Glama
Godot MCP Server

Godot MCP Server

by neondeex

set_theme_font_size

Sets a font size entry for a specific Control class in a Godot Theme resource, letting you define UI text sizes by node type and entry name.

Instructions

Set a font size 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>",
      "size": "<size>"
    },
    "name": "set_theme_font_size"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesFont size entry name
sizeYesFont size in pixels
node_typeYesControl class
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?

No annotations are supplied, so the description carries the full disclosure burden for a mutation tool. It never says whether an existing entry with the same name is overwritten, whether a missing theme or entry causes an error, or whether the change is persisted immediately to the .tres resource – all material for a write operation.

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 or redundancy. It is efficient, though its brevity leaves no room for the operational context the tool actually needs.

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 four-required-parameter mutation tool with no annotations and no output schema, the description is too thin: overwrite semantics, error conditions, and persistence behavior are all unstated. Everything present is already available in the schema, so the description contributes almost no additional coverage.

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 all four parameters (theme_path, node_type, name, size) are already documented in the schema with types and units. The description adds no meaning beyond that – for example it does not clarify the valid range of node_type or how node_type interacts with name.

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 names a specific verb and resource ("Set a font size entry in a Theme resource"), which tells an agent exactly what operation is performed. It does not distinguish this tool from siblings such as set_theme_color or set_theme_stylebox, which share the same pattern and would be candidates for confusion.

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 guidance about when to use this tool versus set_theme_color/stylebox, no prerequisites (e.g. whether the theme must already exist or contain the node_type), and no mention of what happens when the named entry is absent. The agent is left to infer all of this.

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