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

Godot MCP - Full Control

by cxb2523
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

game_bone_pose

Retrieve or update bone positions, rotations, and scales on a Godot Skeleton3D node to inspect or adjust skeletal poses by index or bone name.

Instructions

Get or set bone poses on a Skeleton3D 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": {
      "nodePath": "<nodePath>"
    },
    "name": "game_bone_pose"
  }
}

Input Schema

NameRequiredDescriptionDefault
scaleNoBone scale {x,y,z}
actionNoAction: list, get, or set. Default: list
boneNameNoBone name (alternative to index)
nodePathYesPath to Skeleton3D node
positionNoBone position {x,y,z}
rotationNoBone rotation quaternion {x,y,z,w}
boneIndexNoBone index

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv3.1.0

TDQS

B3.2/5.0
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

The description reveals that the tool can both read and mutate bone poses, which is useful, but it does not disclose side effects, persistence behavior, or what happens when setting pose data. With no annotations provided, the description carries the full burden and only partially covers it.

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?

The description is a single concise sentence with no filler. It front-loads the action ('Get or set') and the target resource, making it scannable and information-dense.

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?

With seven parameters, no annotations, and no output schema, an agent needs more context to invoke this tool correctly—such as how to choose between boneName and boneIndex, which parameters are required for set versus get, and what list/get/set return. The current description leaves too much for the agent to infer.

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 already has a semantic description. The tool description adds general context about bone poses but does not add meaning beyond the schema, which matches the baseline for fully covered parameters.

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

Purpose5/5

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

The description states a specific verb pair ('Get or set') and a precise resource ('bone poses on a Skeleton3D node'), making the tool's function immediately clear. It also distinguishes itself from related sibling tools like game_skeleton_ik because it targets pose values rather than IK solving.

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?

The description provides no guidance on when to use this tool versus alternatives such as game_get_property, game_set_property, or game_skeleton_ik. There is no mention of prerequisites, when get/set/list is appropriate, or how this tool relates to other bone or skeleton tools.

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