unreal-mcp-additional-tools

Overview Schema Source Related Servers Discussions Admin

call_preset_function

Invoke a function exposed in an Unreal Engine Remote Control Preset by specifying the preset name, function name, and optional parameters to trigger the action.

Instructions

Call a function exposed via a Remote Control Preset.

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": {
      "preset_name": "<preset_name>",
      "function_name": "<function_name>"
    },
    "name": "call_preset_function"
  }
}

Input Schema

Name	Required	Description
`parameters`	No	Function parameters
`preset_name`	Yes	Preset name
`function_name`	Yes	Exposed function name

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Aug 21, 2026

TDQS

C2.2/5.0

Behavior2/5

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

No annotations are present to disclose read-only status, destructive potential, or rate limits. The description's verb 'call' implies invocation, but no side effects, permissions, or error behavior are disclosed.

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?

The description is one concise sentence of nine words. It omits examples, parameter details, and usage context, making it too terse to compensate for the sparse annotations and ambiguous preset terminology.

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

Completeness1/5

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

There is no output schema, no behavior on failure, no return value description. The preset concept is undefined, and given the parametrized params object and semantic gap, the agent cannot reliably know what the function returns, whether it is safe, or if it accepts nonstring values. Lacks key information for a call-related tool.

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

Parameters3/5

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

The input schema covers 100% of parameters with names and types (including an 'other properties' object for flexible parameters). However, the description only restates the schema label ('Function parameters') and adds no deeper meaning about specific expected keys, value formats, or the parameter object's structure.

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?

The description states a specific action: 'Call a function' exposed via a Remote Control preset, but it does not identify what a Remote Control preset is, how functions are exposed, or what makes this distinct from sibling tools like get_preset_info, list_presets, or get_preset_property.

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?

No guidance on when to use this tool versus alternatives such as execute_python_code, execute_console_command, or direct preset property getters. There is no mention of context, preconditions, or consequences.

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

Deploy Server