Skip to main content
Glama
Sign In
unreal-mcp-additional-tools

unreal-mcp-additional-tools

by nodormu
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

get_anim_sequence_info

Retrieve animation sequence details including length, frame count, and bone data by providing the AnimSequence asset path.

Instructions

Get info about an animation sequence (length, frames, bone data).

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": {
      "sequence_path": "<sequence_path>"
    },
    "name": "get_anim_sequence_info"
  }
}

Input Schema

NameRequiredDescriptionDefault
sequence_pathYesAnimSequence asset path

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior3/5

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

The description clearly implies a read-only operation ('Get info') and gives some output categories, but it does not disclose error behavior, path validity requirements, or return format details. With no annotations, this is minimal but not misleading.

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

Conciseness5/5

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

The description is a single, front-loaded sentence that conveys the tool's purpose and key output details with no filler or redundancy.

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

Completeness4/5

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

For a one-parameter, no-output-schema tool, the description provides enough context: what it targets and what informational categories to expect. It could be stronger on error cases or path format, but the simplicity of the tool makes this adequate.

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?

The single parameter is fully described in the schema as an 'AnimSequence asset path', so the description adds no additional semantic value beyond the schema. This matches the baseline for high schema coverage.

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?

The description states a specific verb ('Get info') and resource ('animation sequence'), and enumerates the returned data categories (length, frames, bone data). The qualifier 'animation' helps distinguish it from the sibling get_sequence_info tool.

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

Usage Guidelines3/5

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

Usage context is implied: use this when you need metadata about an animation sequence. However, it does not explicitly state when not to use it, nor does it name alternatives such as get_sequence_info for non-animation sequences.

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