Skip to main content
Glama
aadeshrao123

Unreal-MCP

by aadeshrao123

add_key_mapping

Add a key-to-action mapping to an Input Mapping Context in Unreal Engine, binding a physical key to an input action with optional triggers and modifiers.

Instructions

Add a key-to-action mapping to an Input Mapping Context.

Args: context_path: Path to the IMC asset action_path: Path to the InputAction asset key: Key name (e.g. "SpaceBar", "W", "Gamepad_LeftY", "LeftMouseButton") triggers: Optional list of triggers, each {"type": "InputTriggerHold", "properties": {...}} modifiers: Optional list of modifiers, each {"type": "InputModifierNegate", "properties": {...}}

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
keyYes
triggersNo
modifiersNo
action_pathYes
context_pathYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior2/5

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

No annotations provided; description does not disclose side effects (e.g., overwriting existing mapping), error conditions, or prerequisites. Minimal behavioral context for a mutation tool.

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

Conciseness4/5

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

Front-loaded with purpose sentence; Args list is structured and efficient. Slightly verbose with examples but overall concise with no fluff.

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

Completeness3/5

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

Covers parameter requirements and structure adequately but lacks behavioral expectations (e.g., return value, error cases). Output schema exists, so return format is covered, but completeness is moderate.

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

Parameters4/5

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

Schema coverage is 0%; description adds meaningful parameter explanations with examples for key names and structure hints for triggers/modifiers. Compensates well but could detail allowable values more.

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?

Clearly states verb 'Add' and resource 'key-to-action mapping to an Input Mapping Context'. Distinguishes from sibling tools like remove_key_mapping and set_key_mapping by specifying addition.

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?

Implies use for adding a new mapping but does not explicitly state when to use or not use alternatives. No mention of prerequisites or comparison with sibling tools like set_key_mapping.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/aadeshrao123/Unreal-MCP'

If you have feedback or need assistance with the MCP directory API, please join our Discord server