Skip to main content
Glama
unreal-lazy-mcp

unreal-lazy-mcp

by abc11010xyz

get_tool_details

Return a tool's input schema so you can inspect required parameters before invoking it, preventing failed calls. Use find_tools first to discover unknown tools.

Instructions

Return the input schema for a tool. Inspect it before invoke; for a different action use find_tools again if its tool is not yet known. Preserve actual UE refPaths.

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": {
      "toolset": "<toolset>",
      "tool": "<tool>"
    },
    "name": "get_tool_details"
  }
}

Input Schema

NameRequiredDescriptionDefault
toolYes
toolsetYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.9

TDQS

B3.3/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 load; it does convey that the operation is a lookup returning a schema rather than an execution, which is the key behavioral distinction. However, it never states what happens when toolset or tool do not resolve, whether the call is side-effect free, or any constraint on the returned refPaths — meaningful gaps for a two-required-string lookup tool with no annotation coverage.

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?

Three short sentences with the primary purpose front-loaded, so it is appropriately sized and there is no filler. The closing clause about UE refPaths is unexplained and reads as an in-joke rather than actionable instruction, which costs it structure points.

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

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists, so the description need not explain return values, and the pre-invoke workflow cue is the most useful thing an agent needs. Still, with 0% parameter documentation and no failure-mode detail, an agent must guess how toolset and tool interact and what an unresolvable lookup produces.

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?

Schema description coverage is 0%, so the description must compensate and it largely does not. It refers to "a tool" and "its tool" loosely, never explains what the toolset parameter denotes or how the two coordinates combine, and the only additional hint — "Preserve actual UE refPaths" — is unexplained jargon.

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?

"Return the input schema for a tool" gives a specific verb (return) and resource (a tool's input schema), which cleanly separates this schema-lookup tool from invoke (execution) and find_tools (discovery). The trailing sentence about UE refPaths is opaque but does not obscure the core purpose.

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?

"Inspect it before invoke" explicitly states when to call this tool relative to the invoke sibling, and it names find_tools as the alternative when the target tool is not yet known. The guidance is clear in intent, though the phrasing "for a different action use find_tools again if its tool is not yet known" is awkward and leaves the boundary case (tool known, toolset unknown) unaddressed.

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