Skip to main content
Glama
Sign In
Godot MCP Bridge

Godot MCP Bridge

by farrasfadhils
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Local

set_blend_tree_node

Configure blend tree nodes in Godot animation trees to manage animation blending and transitions

Instructions

Configure blend tree node. (Compatibility tool)

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "set_blend_tree_node"
  }
}

Input Schema

NameRequiredDescriptionDefault
timeoutMsNo
autoConnectNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

D1.9/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full burden. It mentions '(Compatibility tool)' implying legacy behavior, but fails to explain mutation scope, persistence, side effects, or the significance of the timeoutMs/autoConnect parameters. Lacks disclosure of what the tool actually modifies.

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

Conciseness2/5

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

Extremely brief (4 words), but this brevity is not virtue—it sacrifices essential documentation. The parenthetical '(Compatibility tool)' consumes space without explanatory value, while critical parameter semantics and behavioral constraints are omitted entirely.

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?

No output schema exists and annotations are absent, yet the description fails to explain return values, error conditions, or the relationship between the generic timeoutMs/autoConnect parameters and blend tree node configuration. Inadequate for a tool with additionalProperties flexibility.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% for both timeoutMs and autoConnect, and the description completely fails to compensate. Critically, the schema declares 'additionalProperties: true', indicating arbitrary configuration properties can be set, yet the description does not mention this extensible behavior or how to use it.

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

Purpose3/5

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

States the tool configures a 'blend tree node' (specific to animation systems), distinguishing it from sibling tools like set_tree_parameter or create_animation_tree. However, 'Configure' is vague regarding which specific attributes are modified or what blend tree means in this context.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines1/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Provides no guidance on when to use this tool versus alternatives like set_tree_parameter or create_animation_tree. The parenthetical '(Compatibility tool)' suggests special usage constraints but offers no explanation of what they are or when this should be preferred/avoided.

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