Skip to main content
Glama

unreal_get_skeletal_mesh_info

Retrieves skeletal mesh information from Unreal Engine projects, enabling AI clients to inspect asset details for animation, rigging, or debugging workflows.

Instructions

Get skeletal mesh 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_skeletal_mesh_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.9/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 discloses almost nothing: it does not say whether the mesh is identified by path, name, or asset reference, nor how heavy the call is. The existence of an output schema relieves it of explaining return values, which is the only thing keeping this above a 1.

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?

It is short, but the brevity reflects under-specification rather than economy: the one sentence duplicates the tool name and conveys zero additional information.

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

Completeness2/5

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

Even for a simple one-parameter lookup with an output schema, the definition is incomplete because the sole required argument is entirely undefined. An agent cannot call this tool correctly without guessing the parameter shape.

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 single parameter is an opaque object literally named "params" with no properties defined. The description offers no hint about what must be passed, so an agent cannot construct the required argument from either source.

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 skeletal mesh info" restates the tool name and title without adding a verb+resource distinction beyond that. With siblings like unreal_get_mesh_info and unreal_get_skeleton_info in the same family, the description gives no basis for telling which resource this actually targets.

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 when to prefer this over unreal_get_mesh_info, unreal_get_mesh_bounds, or unreal_get_skeleton_info. At best the word "Get" implies a read operation.

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