Skip to main content
Glama

validate_anim_state_machine

Read-onlyIdempotent

Inspect an Animation Blueprint state machine without compiling or editing it; reports state/transition counts plus validation errors, warnings, and info.

Instructions

Check a state machine of an Animation Blueprint by node counts, without compiling or changing it: no states is an error, one an info, several without transitions a warning. state_count counts states only (conduits and aliases excluded), transition_count the transition nodes; compile_anim_blueprint is the check that the machine compiles.

Returns: { is_valid, errors[], warnings[], info[], state_count, transition_count }

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
machine_nameNoAlias of `state_machine_name` (same value, same meaning). Accepted because sibling tools spell this parameter differently; prefer `state_machine_name`.
blueprint_nameNoAlias of `anim_blueprint_path` (same value, same meaning). Accepted because sibling tools spell this parameter differently; prefer `anim_blueprint_path`.
state_machine_nameNoName of a state machine in the top-level AnimGraph, matched without case (see list_anim_state_machines).
anim_blueprint_pathNoAsset path of the UAnimBlueprint

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.2.0
    • changedInput schema / properties / state_machine_name / description
      Previous value: -"Name of the state machine"New value: +"Name of a state machine in the top-level AnimGraph, matched without case (see list_anim_state_machines)."
  2. First observedv1.1.0

TDQS

A4.6/5.0
Behavior5/5

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

Annotations cover the read-only/idempotent profile, but the description adds substantial behavior: it does not compile or mutate, and it maps node counts to severities (no states=error, one=info, several without transitions=warning), and clarifies that conduits and aliases are excluded from state_count.

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?

Dense but front-loaded with the action and scoping clause; the severity rules and return shape are compact. The returns line is slightly run-on but earns its place given no output schema exists.

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

Completeness5/5

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

With no output schema, the description supplies the return shape (is_valid, errors, warnings, info, state_count, transition_count), and combined with the severity rules and the compile sibling pointer, an agent has everything needed to call and interpret this tool.

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 coverage is 100%, so both the canonical and alias parameters are fully documented in the schema, making 3 the baseline. The description's counting rules (states only, conduits/aliases excluded) add meaning about results rather than about the input parameters themselves.

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?

States a specific verb+resource ('Check a state machine of an Animation Blueprint') and a precise mechanism ('by node counts'), immediately distinguishing it from the sibling compile_anim_blueprint which it names.

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

Usage Guidelines5/5

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

Explicitly states the boundary ('without compiling or changing it') and routes the agent: 'compile_anim_blueprint is the check that the machine compiles.' The when-to-use vs alternative is fully specified.

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