Skip to main content
Glama

unreal_get_mesh_info

Retrieve static mesh information from Unreal Engine 5 projects so you can inspect mesh details before editing or spawning actors.

Instructions

Get static 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_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

C2.1/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full burden, and it discloses nothing beyond the one-word implication of "get" being a read. It says nothing about permissions, cost, side effects, or scope (single asset vs. all meshes), all of which the agent needs for a tool with zero structured behavioral metadata.

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?

Four words is not conciseness here, it is under-specification; there is no structure to front-load because nothing substantive is stated. The length is appropriate for a trivial tool but this tool has an opaque parameter and many near-identical siblings.

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?

An output schema exists, so return values need not be explained, which relieves some burden. But for a tool with a fully opaque required parameter and ambiguous siblings, the definition omits the input contract and any disambiguation, so it is not complete enough to invoke reliably.

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 untyped "Params" object with 0% schema description coverage, so the schema gives no meaning at all. The description does not mention what goes into params (asset path, name, filter?), leaving the only parameter completely undocumented in both sources.

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

Purpose3/5

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

States a verb and resource ("Get static mesh info"), so an agent can tell it retrieves something about static meshes. However, "info" is undefined and the description does nothing to distinguish it from close siblings like unreal_get_skeletal_mesh_info, unreal_get_mesh_bounds, unreal_get_mesh_materials, or unreal_get_mesh_sections.

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 any alternative. With a dense sibling set covering bounds, materials, sections, and skeletal meshes, the absence of routing guidance forces the agent to guess which getter to call.

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