Skip to main content
Glama

ui_set_layout

Set UI control layout properties in a Godot scene, including anchor preset, position, size, and custom anchors.

Instructions

Set layout properties for a UI control.

Category: UI

Args: project_path: Path to the Godot project directory scene_path: Path to the scene file (relative to project) node_path: Path to the control node anchor_preset: Preset name (FullRect, CenterTop, Center, etc.) position: Position as JSON array [x, y] size: Size as JSON array [width, height] anchors: Custom anchors as JSON object {"left": 0, "top": 0, "right": 1, "bottom": 1}

Returns: Success message or error description

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
project_pathYes
scene_pathYes
node_pathYes
anchor_presetNo
positionNo
sizeNo
anchorsNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior2/5

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

No annotations provided, so description carries full burden. It only states 'Set layout properties' and returns success/error. No details on side effects (saves? modifies scene?), reversibility, or required state (project open?). Vague behavioral disclosure.

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

Conciseness5/5

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

Descriptions is concise with structured sections (brief sentence, category, args, returns). Every sentence adds value, no redundancy. Front-loaded with purpose.

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

Completeness4/5

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

All parameters and return value are explained. However, missing usage context (preconditions, interaction between anchor_preset and anchors) and behavioral details. Output schema exists, so return value clarity is less critical. Mostly complete.

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

Parameters5/5

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

Schema description coverage is 0%, and the description compensates fully by explaining each parameter's purpose, format (e.g., JSON array for position, JSON object for anchors), and examples (e.g., anchor_preset values). Adds significant meaning beyond schema.

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

Purpose5/5

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

The description clearly states the tool sets layout properties for a UI control, distinguishing it from UI addition tools (ui_add_container, ui_add_control). The verb 'Set' and resource 'layout properties' are specific.

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?

No guidance on when to use this tool vs alternatives, no prerequisites mentioned (e.g., control must exist, scene must be open). The description lacks context for proper selection among siblings.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/ChanceFlow/godot-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server