Skip to main content
Glama

unreal_get_skeleton_info

Retrieves skeleton info from Unreal Engine assets, enabling AI clients to inspect bone hierarchies and rig data before editing or automating animation workflows.

Instructions

Get skeleton info.

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

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 carries the full behavioral burden, and it discloses nothing about permissions, cost, or scope. The verb "Get" weakly signals a read-only retrieval, but the description says nothing about what is returned or what the required params object must contain.

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?

The single sentence is short but front-loads nothing useful; it is under-specification rather than conciseness. There is no wasted wording because there is almost no wording at all.

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?

With no annotations, a fully undocumented required parameter, and no output description, the definition is inadequate for invoking the tool correctly. The existence of an output schema covers return values, but nothing else in the definition compensates for the missing purpose and parameter detail.

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?

Schema description coverage is 0% and the sole parameter is an opaque object literally named "params" with no properties defined. The description offers no clarification, leaving the agent with zero information about what to pass for a required argument.

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?

"Get skeleton info" merely restates the tool name and adds no resource qualifier beyond the word "skeleton." It gives an agent no way to distinguish this from siblings such as unreal_get_skeleton_assets or unreal_get_skeletal_mesh_info, which plausibly return overlapping data.

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 stated prerequisites, and no mention of when a sibling tool would be the better choice. The agent must guess whether this returns bone hierarchies, sockets, or metadata versus the asset list covered by unreal_get_skeleton_assets.

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