Skip to main content
Glama
unreal-lazy-mcp

unreal-lazy-mcp

by abc11010xyz

list_toolsets

Lists Unreal Engine toolsets and their IDs/tool counts, optionally filtered by a query, to help identify relevant tool groups before invoking editor tools.

Instructions

List Unreal toolsets (id and tool count). With query, return only related toolsets. find_tools is usually more direct.

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": "list_toolsets"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.9

TDQS

A3.8/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full behavioral burden; it does disclose the return shape (id plus tool count) and that filtering is optional. It says nothing about read-only semantics, result volume, pagination, or what an empty query returns, which are the remaining behaviors an agent would want for a listing tool.

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?

Three short sentences, front-loaded with the purpose, then the parameter behavior, then the alternative. No filler; every clause carries information.

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

Completeness4/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 elaboration, and a one-optional-parameter read tool is inherently simple. The description covers purpose, filtering, and the sibling alternative; only the unfiltered default behavior and result-size expectations are left implicit.

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

Parameters3/5

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

Schema description coverage is 0% for the single `query` parameter, so the description must compensate. It does explain the parameter's effect ('return only related toolsets'), but not the matching semantics (substring vs. relevance), nor what the null default does, so it only partially fills the gap.

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?

States a specific verb and resource ('List Unreal toolsets') and even names the returned fields (id and tool count), which lets an agent predict the payload. It distinguishes itself from find_tools, though it does not contrast with get_tool_details, so differentiation is partial rather than complete.

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?

'With `query`, return only related toolsets' defines the filtering condition, and 'find_tools is usually more direct' names an alternative and a preference. It stops short of stating the positive case for choosing list_tools (e.g., browsing/discovery of all toolsets), leaving that to inference.

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