Skip to main content
Glama

unreal_get_animation_notifies

Retrieve animation notifies from Unreal Engine animations to inspect timing events and trigger gameplay logic.

Instructions

Get animation notifies.

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": {
      "params": "<params>"
    },
    "name": "unreal_get_animation_notifies"
  }
}

Input Schema

NameRequiredDescriptionDefault
paramsYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

D1.7/5.0
Behavior1/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, yet it discloses nothing: not whether it is read-only, what scope of notifies is returned, whether an asset context is required, or whether results are filtered. A single tautological sentence leaves the agent with zero behavioral signal.

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

Conciseness3/5

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

It is short and front-loaded, so there is no wasted wording, but that brevity reflects under-specification rather than efficient communication. The single sentence provides no structure such as scope, inputs, or return behavior.

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

Completeness1/5

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

An output schema exists, so return values need not be explained, but the definition still fails on the input side: an opaque required 'params' object with no description and no annotations. For a tool whose only argument is untyped, the description must do far more than echo the name.

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?

The sole parameter is an untyped 'params' object with 0% schema description coverage, and the description says nothing about what it must contain (asset path, name filter, etc.). With the only parameter completely opaque in both schema and prose, the agent cannot construct a valid call from this definition.

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

Purpose2/5

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

The description is essentially a restatement of the tool name: 'Get animation notifies' adds no noun detail beyond the identifier. It does not say what a 'notify' is in Unreal terms, nor how this differs from siblings such as unreal_add_animation_notify or unreal_get_animation_info.

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 prerequisite context (e.g. an asset or animation blueprint that owns the notifies), and no indication of how this relates to the add/create siblings. The agent must infer everything from the name.

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