Skip to main content
Glama

find_tools

Read-onlyIdempotent

Search this MCP server's Unreal Editor tool catalog by keywords or domain to identify matching tools and their parameters before choosing, describing, or calling one.

Instructions

Searches this server's 1585 Unreal Editor tools and returns the best matches, each with its name, domain, parameters (* marks a required one) and the first sentence of its description. Use it before guessing a tool name or writing Python; when you already know the name, skip it: describe_tool and call_tool take the name directly.

Examples: {"query": "material parameter"} searches every tool, {"query": "landscape", "domain": "Level"} searches one domain, and {"domain": "Water"} lists a domain's tools. Each query word scores on a whole word of a tool's name first, then the start of one, then the domain, then the description, and a tool that matches more of the words ranks higher, so a query that spells a tool's name, such as "spawn actor", puts it first. limit (default 25, up to 300) caps the list; more then says how many matched beyond it, and a query that matches nothing gets next, with what to try.

With no arguments it lists the 57 domains, each with what it covers and its size, and the packs with their tools. It only reads the catalog, so it is cheap to repeat. Then describe_tool gives a match's full schema and call_tool runs it, or enable_toolset adds its pack or domain to your tool list.

Returns: { success, matches: int, tools: [{ name, domain, params?, summary }], more?: string, next?: string } -- with no arguments { success, total_tools, domains: [{ domain, description, tools }], packs: [{ pack, description, tools }], next }. An unknown domain is an error that lists the domains.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "find_tools"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoHow many tools to return (default 25, at most 300).
queryNoWords from the tool's name or purpose, e.g. "spawn actor" or "material parameter". A plural also finds the singular.
domainNoOnly this domain's tools; without a query, lists them all.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv2.11.0
    • changedInput schema / properties / domain / enum
      Previous value: -[
      -  "AI",
      -  "Analysis",
      -  "Animation",
      -  "Asset",
      -  "Audio",
      -  "Audit",
      -  "BehaviorTree",
      -  "Blueprint",
      -  "Camera",
      -  "Chooser",
      -  "Config",
      -  "DataAsset",
      -  "Documentation",
      -  "Editor",
      -  "Engine",
      -  "Export",
      -  "GameFeatures",
      -  "GameFramework",
      -  "GameplayAbilities",
      -  "GameplayBehavior",
      -  "GameplayDebugger",
      -  "GameplayTags",
      -  "GeometryScript",
      -  "Graphics",
      -  "HLOD",
      -  "Input",
      -  "Interchange",
      -  "Level",
      -  "Lighting",
      -  "Management",
      -  "Mass",
      -  "Material",
      -  "Mesh",
      -  "Meta",
      -  "Navigation",
      -  "Networking",
      -  "Optimization",
      -  "Packaging",
      -  "Performance",
      -  "Physics",
      -  "Procedural",
      -  "Reflection",
      -  "Replication",
      -  "SaveGame",
      -  "SmartObjects",
      -  "StateTree",
      -  "Subsystem",
      -  "SubsystemAuthoring",
      -  "Testing",
      -  "Timeline",
      -  "Trigger",
      -  "UI",
      -  "USD",
      -  "UVMapping",
      -  "Water"
      -]New value: +[
      +  "AI",
      +  "Analysis",
      +  "Animation",
      +  "Asset",
      +  "Audio",
      +  "Audit",
      +  "BehaviorTree",
      +  "Blueprint",
      +  "Camera",
      +  "Chooser",
      +  "Code",
      +  "Config",
      +  "DataAsset",
      +  "Documentation",
      +  "Editor",
      +  "Engine",
      +  "Export",
      +  "GameFeatures",
      +  "GameFramework",
      +  "GameplayAbilities",
      +  "GameplayBehavior",
      +  "GameplayDebugger",
      +  "GameplayTags",
      +  "GeometryScript",
      +  "Graphics",
      +  "HLOD",
      +  "Input",
      +  "Interchange",
      +  "Level",
      +  "Lighting",
      +  "Management",
      +  "Mass",
      +  "Material",
      +  "Mesh",
      +  "Meta",
      +  "Navigation",
      +  "Networking",
      +  "Optimization",
      +  "Packaging",
      +  "Performance",
      +  "Physics",
      +  "Procedural",
      +  "Reflection",
      +  "Replication",
      +  "SaveGame",
      +  "SmartObjects",
      +  "SourceControl",
      +  "StateTree",
      +  "Subsystem",
      +  "SubsystemAuthoring",
      +  "Testing",
      +  "Timeline",
      +  "Trigger",
      +  "UI",
      +  "USD",
      +  "UVMapping",
      +  "Water"
      +]
  2. Addedv2.5.0

TDQS

A5/5.0
Behavior5/5

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

Beyond the readOnlyHint and idempotentHint annotations, the description discloses that it only reads the catalog, is cheap to repeat, has scoring behavior, returns a more count beyond limit, emits next guidance when nothing matches, and treats an unknown domain as an error that lists domains. That is substantial operational context not captured by the annotations alone.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is front-loaded with purpose and usage, then followed by examples, ranking details, limits, no-argument behavior, and return shape. Despite its length, every section supplies operational guidance an agent needs to call the tool correctly, with no evident filler.

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?

For a discovery tool with no output schema, the description fully specifies the return structure for both query and no-argument modes, including matches, more, next, domains, packs, and error behavior. It is complete enough that an agent can decide when to call it and interpret the result without additional documentation.

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

Parameters5/5

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

Schema coverage is 100%, but the description adds meaningful semantics beyond the schema: query words are matched against name, domain, and description with a specific ranking order, limit defaults to 25 and caps at 300, and a domain-only call lists that domain's tools. It also explains no-argument behavior and unknown-domain errors, which are not fully conveyed by the parameter definitions 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?

The description states a specific verb and resource: it searches this server's Unreal Editor tool catalog and returns the best matches with name, domain, parameters, and summary. It clearly distinguishes itself from describe_tool and call_tool by saying when the tool name is already known, those siblings take the name directly.

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

Usage Guidelines5/5

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

It gives explicit when-to-use guidance: use before guessing a tool name or writing Python, and skip when the name is already known because describe_tool and call_tool accept it directly. It names the relevant alternatives and explains follow-up actions through describe_tool, call_tool, and enable_toolset.

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