Skip to main content
Glama

unreal_list_tools

Lists tools registered in the Unreal Engine plugin, enabling users to discover available editor actions and capabilities.

Instructions

List tools registered in the Unreal plugin.

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

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 supplied, so the description carries the full burden of behavioral disclosure. 'List' implies a read, but the description says nothing about whether the result is paginated, how large it may be, whether it requires an editor connection, or what happens on failure. The presence of an output schema covers return values but not these operational traits.

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 sentence is front-loaded and contains no filler, which is structurally sound. However, the brevity comes from under-specification rather than from disciplined editing, so it does not earn full marks.

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?

The tool is simple and the output schema relieves the description of explaining return values, but with no annotations, an undocumented required params object, and no usage routing, an agent still lacks enough to call it confidently relative to its siblings.

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 required parameter is a bare 'params' object with 0% schema description coverage, and the description does not explain what belongs in it or whether it can be omitted. For a one-parameter tool with an opaque wrapper, the description should have said what the params object carries.

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 gives a specific verb and resource: list tools registered in the Unreal plugin. That is unambiguous about what comes back, but it offers no differentiation from the many sibling list tools (animations, assets, levels), so an agent must infer that 'tools' means plugin-registered tools rather than the editor's other listable entities.

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 guidance on when to use this versus other listing tools, no preconditions, and no statement about when it is not appropriate. The agent gets a purpose statement and nothing about selection context.

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