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

Godot MCP - Full Control

by cxb2523
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

game_path_2d

Create and manage Path2D/Curve2D nodes in Godot by adding or setting points, so AI assistants can define 2D paths and curves for game scenes.

Instructions

Path2D/Curve2D management and AnimatedSprite2D

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_2d"
  }
}

Input Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv3.1.0

TDQS

D1.9/5.0
Behavior1/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, and it discloses nothing: not whether create/add_point mutate the scene, whether it targets the running game or the editor scene, or what permissions/state are required. It also advertises AnimatedSprite2D handling that no parameter or action in the schema can express, which actively misleads an agent about capability.

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

Conciseness3/5

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

It is short, but short here comes from under-specification rather than economy, and it is not structured as a usable sentence. The single clause is front-loaded but the trailing 'and AnimatedSprite2D' is wasted and misleading rather than earning its place.

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

Completeness1/5

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

This is a six-parameter tool with nested point objects, multiple actions spanning create and read, no annotations and no output schema. A six-word fragment covering two resource names leaves the agent without the minimum needed to invoke it correctly.

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 is already documented in the schema; this sets the baseline at 3. The description adds no extra meaning about point formats, nodePath conventions, or how parentPath is resolved, so it neither compensates nor detracts.

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

Purpose2/5

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

The description is a noun-phrase label, 'Path2D/Curve2D management and AnimatedSprite2D', with no verb and no statement of what the tool actually does. It hints at a resource family (2D paths/curves) but does not distinguish it from siblings such as game_path_3d or game_navigate_path, and the AnimatedSprite2D clause is unsupported by anything in the schema.

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 prerequisites, and no pointer to an alternative. An agent must infer from the action enum alone whether this is the right tool versus game_path_3d or game_navigate_path.

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