Skip to main content
Glama
Sign In
Godot MCP - Full Control

Godot MCP - Full Control

by cxb2523
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

game_path_3d

Create Path3D/Curve3D nodes and add, set, or retrieve curve points to build and adjust 3D paths in Godot scenes.

Instructions

Create Path3D/Curve3D and manage curve points

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": {
      "action": "<action>"
    },
    "name": "game_path_3d"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNoNode name
pointNoSingle point {x,y,z}
actionYesAction: create, add_point, set_points, get_points
pointsNoArray of points [{x,y,z},...]
nodePathNoPath3D node path (for add/set/get)
parentPathNoParent node path

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv3.1.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 burden of behavioral disclosure. It never states that this is a mutating operation on the scene tree, that add_point/set_points overwrite existing curve data, that create requires a parent path, or that get_points is a safe read - all critical since the same tool mixes reads and writes behind an action parameter.

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 eight-word sentence with no filler, and the primary create capability is front-loaded before the point-management clause. It is efficient, though the terseness leaves structural gaps that the other dimensions penalize.

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?

This is a six-parameter, action-dispatching tool with nested point objects, no annotations, and no output schema, yet the description does not explain which parameters apply to which action (name/parentPath for create, nodePath/point for add_point, etc.). For a multi-mode tool, that mapping is the single most important thing an agent needs.

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 every parameter including the action enum values is already documented in the schema; the description only loosely gestures at points and creation. Baseline 3 applies since the schema does the heavy lifting and the description adds no per-action parameter requirements.

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 pair, 'Create Path3D/Curve3D', plus a secondary capability, 'manage curve points'. The '3D' qualifier implicitly distinguishes it from the sibling game_path_2d, though the description never says so 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?

There is no guidance on when to choose this tool over game_path_2d, game_navigate_path, or game_gridmap, no prerequisites such as an open scene or existing parent, and no statement of what happens if the node path does not exist. 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