Skip to main content
Glama
Godot MCP Server

Godot MCP Server

by neondeex

get_tree_parameter

Retrieves a parameter value from a Godot AnimationTree by node and parameter path, helping AI inspect and debug animation state.

Instructions

Get a parameter value from an AnimationTree.

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>"
    },
    "name": "get_tree_parameter"
  }
}

Input Schema

NameRequiredDescriptionDefault
node_pathYesPath to the AnimationTree
parameterYesParameter path

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 provided, so the description carries the full behavioral burden. 'Get' implies a safe read, but the description says nothing about permissions, error behavior for an invalid node_path or parameter path, or what is returned. For a tool with zero annotation coverage this leaves real gaps.

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 front-loaded sentence with no filler; the resource and action come first. It is efficient, though its terseness borders on under-specification for a tool with no annotations.

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

Completeness3/5

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

For a simple two-parameter read tool with full schema coverage and no output schema, the definition is minimally viable. However, it does not state the return shape (e.g., value plus type) or what happens on a missing parameter, which an agent would want before calling it.

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 both required parameters (node_path, parameter) are already documented in the schema. The description adds no format details—such as whether node_path is scene-relative and what a parameter path looks like—so it earns only the baseline.

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?

States a specific verb and resource: 'Get a parameter value from an AnimationTree.' An agent can immediately tell this is a read of an animation-tree parameter, and the 'get' framing implicitly contrasts with the sibling set_tree_parameter. It stops short of naming or explicitly differentiating from that sibling.

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 mention of alternatives such as set_tree_parameter or the scene-tree getters. The only signal is the verb 'Get', which the agent must interpret on its own.

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