Skip to main content
Glama

unreal_get_input_settings

Retrieve Unreal Engine input settings to inspect key bindings, axis mappings, and action mappings for configuration review or troubleshooting.

Instructions

Get input settings.

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

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 disclosure burden, yet it says nothing about read semantics, permissions, or what the call returns beyond the bare verb "Get". The verb weakly implies a read-only operation, but nothing about side effects, failure modes, or required editor state is stated.

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 that shortness reflects under-specification rather than economy; it is a four-word restatement of the title with no front-loaded substance because there is no substance to front-load.

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 described, but the mandatory and undocumented "params" argument makes the definition uncallable without guesswork. For a settings-retrieval tool sitting among many similarly named siblings, the description does far too little to make the call actionable.

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 required parameter is an untyped "params" object with no properties described. The description adds no meaning whatsoever about what must go inside it, leaving the required input completely opaque.

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 input settings" only restates the tool name; it adds no scope, no detail about which input settings (bindings, axis configs, action mappings) are returned, and no differentiation from the nearby unreal_get_input_mappings or unreal_get_engine_settings siblings. An agent learns nothing beyond the identifier it already has.

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 exclusory condition, and no mention of an alternative tool. The reader cannot tell from the description whether this overlaps with unreal_get_input_mappings or unreal_get_project_settings.

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