Skip to main content
Glama
Godot MCP Server

Godot MCP Server

by neondeex

set_tree_parameter

Sets a parameter on an AnimationTree node, such as blend amount or condition, to control animation behavior in Godot.

Instructions

Set a parameter on an AnimationTree (e.g. blend position, condition).

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>",
      "parameter": "<parameter>",
      "value": "<value>"
    },
    "name": "set_tree_parameter"
  }
}

Input Schema

NameRequiredDescriptionDefault
valueYesNew value for the parameter
node_pathYesPath to the AnimationTree
parameterYesParameter path (e.g. parameters/blend/blend_amount)

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 are supplied, so the description carries the full behavioral burden, yet it only implies mutation via "Set". It does not say what happens when node_path or parameter is invalid, whether the change is undoable, whether the tree must be active, or whether the write is immediate versus queued for the next frame.

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 short sentence with the action and target front-loaded and zero filler. It is efficient, though the brevity reflects thin content rather than disciplined editing of richer material.

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 three-parameter mutation tool with no annotations and no output schema, the description leaves out error behavior, preconditions, and any indication of what the call returns or confirms. The schema covers parameter formats, but the operational context an agent needs before calling is largely absent.

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 all three parameters are already documented, including the example parameter path format. The description adds only a light hint about the kinds of values involved (blend position, condition) and no new syntax, units, or constraints, so the baseline of 3 applies.

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 gives a specific verb plus resource ("Set a parameter on an AnimationTree") and clarifies the kind of parameter with examples (blend position, condition), which distinguishes it clearly from read-only siblings such as get_tree_parameter. It stops short of naming that sibling or any other alternative, so differentiation is inferred rather than stated.

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 explicit when-to-use or when-not-to-use guidance, no mention of the counterpart get_tree_parameter for reading values, and no stated preconditions (tree must exist, parameter path must be valid, tree must be in the scene). The only hint of context is the parenthetical example of parameter kinds, which leaves routing entirely to inference.

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