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

Godot MCP - Full Control

by cxb2523
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

game_create_joint

Create a physics joint between two Godot bodies to constrain their movement, with support for pin, spring, groove, hinge, cone, and slider joint types.

Instructions

Create a physics joint between two bodies

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": {
      "parentPath": "<parentPath>",
      "jointType": "<jointType>"
    },
    "name": "game_create_joint"
  }
}

Input Schema

NameRequiredDescriptionDefault
lengthNoLength (spring_2d, groove_2d)
dampingNoSpring damping (spring_2d)
softnessNoSoftness (pin_2d)
jointTypeYesJoint type: pin_2d, spring_2d, groove_2d, pin_3d, hinge_3d, cone_3d, slider_3d
nodeAPathNoPath to first body
nodeBPathNoPath to second body
stiffnessNoSpring stiffness (spring_2d)
parentPathYesParent node path for the joint

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?

There are no annotations, so the description carries the full burden of disclosing behavioral traits. It only states the basic operation and omits important context such as scene mutation, required node paths, joint type constraints, or whether the operation can be undone.

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?

The description is a single, direct sentence with no filler, and it is front-loaded with the key action and target. However, it may be too terse for a tool with eight parameters, leaving room for additional useful context without adding bloat.

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?

For a tool with eight parameters, no annotations, and no output schema, this description is thin. It does not explain return values, prerequisites, joint type behavior, or how the operation affects the scene, so an agent lacks enough context to use the tool confidently beyond the parameter list.

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 the schema already documents all parameters. The description adds minimal semantic value by indicating the joint connects two bodies, which weakly maps to nodeAPath and nodeBPath, but it does not meaningfully elaborate beyond the schema.

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 uses a specific verb ('Create') and identifies the resource ('physics joint') and the target objects ('between two bodies'). It is clear at a high level, though it does not explicitly distinguish itself from related physics/sibling tools.

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?

No guidance is given about when to use this tool versus alternatives like game_physics_body, game_add_collision, or other joint-related operations. Prerequisites such as the bodies existing in the scene are not mentioned.

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