Skip to main content
Glama

unreal_get_input_mappings

Retrieves input action and axis mappings from an Unreal Engine 5 project, enabling AI clients to inspect configured controls.

Instructions

Get input action/axis mappings.

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

Input Schema

NameRequiredDescriptionDefault
paramsYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.4/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 burden of behavioral disclosure, and it provides none. It does not confirm read-only behavior, state what context (project, asset, editor session) must be open, or note any preconditions. The only mitigating factor is that an output schema exists, so return structure need not be described.

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

Conciseness3/5

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

It is a single short sentence with zero padding, which is structurally clean. However, the brevity comes at the cost of under-specification rather than efficiency, so it cannot score highly on conciseness.

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?

The tool is simple and an output schema exists, which lowers the bar, but the description still omits the scope of the lookup and says nothing about the opaque required 'params' argument. An agent cannot reliably construct a call from this definition alone.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The schema has one required parameter named 'params' with 0% description coverage and no declared properties, so it is fully opaque. The description adds nothing about what should be passed in that object, leaving the agent to guess at the required payload.

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?

The description names a concrete resource (input action/axis mappings) with an implicit read verb, so the agent can roughly guess the domain. It does not differentiate from the nearby sibling unreal_get_input_settings, and 'Get' plus the resource is close to restating the tool name without adding specificity about scope (project vs. asset vs. world).

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 mention of when not to use it, and no pointer to an alternative such as unreal_get_input_settings. The agent must infer usage purely from the name.

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