Skip to main content
Glama
Godot MCP Server

Godot MCP Server

by neondeex

get_collision_layers_info

Retrieve collision layer names and bitmask configuration from Godot project settings to verify physics layers before configuring collisions or generating game code.

Instructions

Get collision layer names and bitmask configuration from the project settings.

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": "get_collision_layers_info"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.4/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 behavioral burden. It implies read-only via 'Get' and indicates the return content (names, bitmasks), but says nothing about whether the editor or a project must be loaded, whether defaults are included, or whether physics layer indices are global or per-layer-name.

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 front-loaded sentence with no filler; the resource and its source appear immediately.

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 zero-parameter getter with no output schema, the description is close to adequate but leaves the returned structure vague (names plus bitmasks, but not how they are keyed or what the bitmask field is called) and omits any execution precondition.

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

Parameters4/5

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

The tool takes zero parameters, so there is nothing for the description to disambiguate; baseline 4 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?

The description names a specific verb ('Get') and a specific resource ('collision layer names and bitmask configuration'), plus the source ('project settings'). That distinguishes it from the setter siblings such as set_collision_layer_name and set_physics_layers, though it never names those alternatives explicitly.

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

Usage Guidelines3/5

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

Use is only implied: 'Get... from the project settings' signals a read of configured project data, so an agent can infer this is the read counterpart to the collision-layer setters. There is no explicit when-to-use statement, no exclusion, and no mention of prerequisites such as an open project.

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