Skip to main content
Glama
Godot MCP Server

Godot MCP Server

by neondeex

set_collision_layer_name

Assign a human-readable name to a Godot collision layer (1–32) in project settings so developers can identify and manage physics layers more clearly.

Instructions

Set the name of a collision layer in the project settings.

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": {
      "layer": "<layer>",
      "name": "<name>"
    },
    "name": "set_collision_layer_name"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesHuman-readable name for the layer
layerYesLayer number (1-32)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.2/5.0
Behavior2/5

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

No annotations exist, so the description carries the full burden. It implies a mutation of persistent project settings but never says whether the change is saved to disk, whether it is undoable, whether the layer must already exist, or what happens if the layer index is out of range despite the schema's 1-32 hint.

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?

A single short sentence with the action and target front-loaded and no filler. Nothing in it is wasted, though the terseness contributes to gaps scored elsewhere.

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

Completeness5/5

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

Placeholder.

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 coverage is 100% and both parameters are documented, including the 1-32 layer range and the meaning of 'name'. The description adds nothing beyond the schema, so the baseline 3 applies.

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?

Names a specific verb ('Set') and resource ('name of a collision layer in the project settings'), which is enough to distinguish it from layer-related siblings like setup_collision or get_collision_layers_info. It stops short of explicitly contrasting itself with the physics/navigation layer setters, but the resource is unambiguous.

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 when-to-use guidance, no mention of prerequisites (open project, existing layer), and no pointer to alternatives such as set_physics_layers or get_collision_layers_info for inspection. The agent must infer everything from the tool name.

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