Skip to main content
Glama
unreal-lazy-mcp

unreal-lazy-mcp

by abc11010xyz

invoke

Runs an allowlisted Unreal Engine editor tool by toolset and tool name, returning native MCP result blocks and structuredContent for the agent to inspect.

Instructions

Run the selected Unreal tool. Only tools on the configured execution allowlist run (not necessarily read-only). A successful call returns the Native MCP result blocks and structuredContent unchanged; inspect its isError for Native tool failures. Wrapper denials and transport errors return Wrapper status JSON.

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": {
      "toolset": "<toolset>",
      "tool": "<tool>"
    },
    "name": "invoke"
  }
}

Input Schema

NameRequiredDescriptionDefault
toolYes
toolsetYes
argumentsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.9

TDQS

B3.4/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does substantial work: it discloses the allowlist constraint, that tools are 'not necessarily read-only,' that successful calls return Native MCP blocks and structuredContent unchanged, that isError should be inspected, and that wrapper denials/transport errors yield Wrapper status JSON. It still omits any permission or side-effect details beyond the read-only caveat.

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?

The description is compact and front-loaded: purpose first, then constraint, then return/failure semantics. Every sentence adds information, though the second sentence is dense and could be split for readability.

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?

For an execution proxy with no annotations, no output schema, and 0% parameter coverage, the description covers return values and failure modes well but leaves the input parameters underspecified. An agent can call it, but may not know exactly what to put in toolset, tool, and arguments.

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?

Schema description coverage is 0%, so the description must compensate, but it only vaguely references a 'selected' tool and an execution allowlist. It does not explain the distinction between toolset and tool, nor clarify that arguments are forwarded to the native tool, leaving all three parameters semantically thin.

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

Purpose4/5

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

The description opens with a specific verb and resource: 'Run the selected Unreal tool.' It clearly identifies an execution/proxy operation, which implicitly contrasts with the discovery-oriented siblings (find_tools, get_tool_details, list_toolsets), though it never names them explicitly.

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?

It states a key constraint—only allowlisted tools may run—which implies a precondition, but it gives no explicit when-to-use guidance, no instruction to first discover tools via siblings, and no exclusions. Usage is inferable rather than guided.

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