Skip to main content
Glama

unreal_add_animation_notify

Adds an animation notify to a skeletal animation asset so gameplay events can trigger at chosen points in the animation.

Instructions

Add an animation notify.

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_add_animation_notify"
  }
}

Input Schema

NameRequiredDescriptionDefault
paramsYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

D1.8/5.0
Behavior2/5

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

No annotations are supplied, so the description bears the full disclosure burden and delivers almost nothing. "Add" implies mutation, but it does not say whether the change is persisted to the asset, what permissions or editor state are required, whether duplicate notifies are allowed, or what happens on failure.

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?

One short sentence is trivially concise but is under-specified rather than efficient; there is no front-loaded information because there is essentially no information. Conciseness credit does not apply when the brevity comes from omitting required detail.

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?

For a mutation tool that takes a free-form parameter blob, requires that blob, and has zero annotation coverage, the description supplies none of the context needed to invoke it. An output schema exists, so return values need not be explained, but the input contract is entirely undisclosed.

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 single required parameter is an opaque "params" object with 0% schema description coverage and no type information beyond a title. The description adds no meaning about what fields that object must contain (notify name, class, time, track), leaving the agent unable to construct a valid call.

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?

"Add an animation notify" restates the tool name almost verbatim and gives no more specificity than the identifier already does. It never says what an animation notify is attached to (a sequence, montage, or blueprint) or what the operation produces, so it does not distinguish itself from siblings such as unreal_get_animation_notifies or unreal_create_animation_montage.

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 an alternative. An agent must infer from the verb alone that this is a write operation on animation notifies and cannot tell when to prefer it over unreal_get_animation_notifies or unreal_create_animation_montage.

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