Skip to main content
Glama
Godot MCP Server

Godot MCP Server

by neondeex

set_physics_layers

Configure collision layer and mask bitmasks on a physics body node to control which objects collide and interact in Godot.

Instructions

Set the collision layer and mask bitmasks on a physics body node.

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": {
      "node_path": "<node_path>"
    },
    "name": "set_physics_layers"
  }
}

Input Schema

NameRequiredDescriptionDefault
maskNoCollision mask bitmask
layerNoCollision layer bitmask
node_pathYesNode path

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 exist, so the description carries the full disclosure burden, yet it only says 'set'. It does not state whether this requires an existing physics body, whether the bitmask overwrites existing values, whether changes persist or are editor-session-only, or what happens on invalid node paths — all critical for a mutation tool.

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 zero filler. It is efficient, though its brevity is part of why behavioral and usage context is missing rather than a stylistic flaw in itself.

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 three-parameter mutation with no annotations and no output schema, the description is thin: it omits error conditions, whether both layer and mask should be supplied together, and the effect of omitting the optional params. The complete input schema partially compensates but not fully.

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%, so node_path, layer, and mask are already documented. The description only restates that layer/mask are bitmasks without adding format details (e.g. decimal vs. bit-index, default behavior when a parameter is omitted).

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?

States a specific verb (Set) plus the exact resource and fields (collision layer and mask bitmasks) and the target object (physics body node). It implicitly distinguishes itself from set_navigation_layers by naming 'collision' and 'physics', but never contrasts with any sibling explicitly.

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?

Provides no when-to-use guidance, no prerequisites (e.g. the node must already be a physics body), and no mention of alternatives such as setup_physics_body or get_collision_layers_info. An agent must infer the context entirely.

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