Skip to main content
Glama

unreal_get_errors

Retrieve recent Unreal Engine and plugin errors so AI clients can diagnose editor issues and identify failing components.

Instructions

Get recent engine/plugin errors.

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

Input Schema

NameRequiredDescriptionDefault
paramsYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.6/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full burden and does very little with it. 'Recent' is the only behavioral hint, and it is undefined (how recent? how many? any rate limits or editor-state prerequisites?), leaving the agent guessing at result scope.

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 single short sentence is front-loaded and wastes no words, but its brevity comes at the cost of specification rather than being an efficient summary of richer content. It is tersely adequate rather than well-structured.

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 explained, but the description still omits the meaning of 'recent', the required 'params' argument's structure, and any environment prerequisites. For a tool with zero annotation coverage and an undocumented required parameter, this is not enough to call it reliably.

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 single parameter 'params' has 0% schema description coverage and is described nowhere in the text, so the agent has no idea what to pass or whether it is optional-shaped despite being required. The description adds no meaning beyond the opaque schema.

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 names a specific verb and resource ('Get ... engine/plugin errors') and adds a recency scope ('recent'). However, it does not explicitly distinguish itself from the close sibling unreal_get_compile_errors, so an agent must infer that 'engine/plugin' excludes compile errors.

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 exclusions, and no naming of alternatives such as unreal_get_compile_errors. An agent knows roughly what the tool fetches but not when to prefer it over the sibling error tools.

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