Skip to main content
Glama
unreal-lazy-mcp

unreal-lazy-mcp

by abc11010xyz

find_tools

Search Unreal Engine MCP editor tool candidates for the next action in a user task, so agents choose an appropriate tool before invoking it and reduce token usage and failed calls.

Instructions

Find Unreal Engine tool candidates for the NEXT action in a user's task, not necessarily the whole task. In query, describe the specific action using the user's actual intent; preserve quoted text, proper nouns, asset names and /Game/... paths exactly. Pass short English action/object keywords in english_keywords when useful for non-English text. Search again only for a different step/capability; never retry an identical query just to fish for an answer. Blueprint graph logic: BlueprintTools.write_graph_dsl writes and compiles a whole graph in one call (read get_graph_dsl_docs first) - usually fewer calls than adding nodes and pins one by one.

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": {
      "query": "<query>"
    },
    "name": "find_tools"
  }
}

Input Schema

NameRequiredDescriptionDefault
kNoMaximum number of candidates.
queryYesThe user's request, unchanged, in its original language.
english_keywordsNoShort English search keywords (action, object, capability). Provide them when the request is not in English.

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.9

TDQS

A4.2/5.0
Behavior3/5

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

With no annotations, the description must carry the behavioral load. It discloses the retry policy and the 'candidates, not answers' nature of the result, but never states that the call is side-effect-free or how candidates should be consumed, which matters for a discovery tool feeding a pipeline.

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?

Front-loaded with the core scope, then query rules, then the retry rule, then a blueprint aside. Every sentence is a rule rather than filler, though the BlueprintTools paragraph is tangential for a discovery tool and could be trimmed.

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

Completeness5/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 no explanation. For a three-parameter search tool the description covers scope, query formulation, language handling, and re-search discipline — everything needed to invoke it correctly.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3, and the description earns above that by prescribing query construction: describe the specific action, preserve quoted text, proper nouns, asset names and /Game/ paths verbatim, and use english_keywords for non-English input. Only `k` is left to the schema alone.

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

Purpose5/5

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

States a specific verb and resource ('Find Unreal Engine tool candidates') and sharpens the scope with 'for the NEXT action in a user's task, not necessarily the whole task.' That framing lets an agent tell this apart from a details/invoke tool without opening a schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives concrete when-to-use (the next step of a task), a when-not-to (never retry an identical query to fish for an answer), and a workflow alternative (prefer write_graph_dsl over node-by-node assembly). It stops short of explicitly routing to siblings like get_tool_details or list_toolsets, so the post-search path is left implicit.

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