Skip to main content
Glama
Sign In
Unreal-MCP

Unreal-MCP

by aadeshrao123
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Local

get_available_materials

Retrieve a list of materials available for applying to objects, with filtering by content path, name substring, and engine materials.

Instructions

List materials that can be applied to objects.

Args: search_path: Content Browser root to scan (e.g. "/Game/Weapons/") include_engine_materials: Include /Engine/ materials in results filter: Case-insensitive substring match on material asset name max_results: Cap on returned entries. 0 = unlimited (use sparingly)

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

Input Schema

NameRequiredDescriptionDefault
filterNo
max_resultsNo
search_pathNo/Game/
include_engine_materialsNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.2.1

TDQS

A4/5.0
Behavior3/5

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

No annotations exist. The description explains parameters but does not disclose behavioral traits such as whether results are sorted, if duplicates are possible, or if the list includes only materials currently used. The 'use sparingly' note on max_results=0 provides minor behavioral insight, but overall depth is lacking.

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 concise, with a clear purpose sentence followed by a labeled Args section. Every sentence adds value, and it is front-loaded with the main action. No redundant phrasing.

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?

Given the presence of an output schema (not shown), the description does not need to detail return values. However, it lacks clarification on what 'available' means (e.g., only in content browser, or including those in maps). It is mostly complete for a list tool with good sibling context.

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 0%, so the description must compensate. It explains each parameter: search_path (root to scan), include_engine_materials (include engine materials), filter (case-insensitive substring), max_results (cap). This provides meaningful context beyond the schema.

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 clearly states 'List materials that can be applied to objects' which is a specific verb+resource. It distinguishes from siblings like 'create_material' (creates) and 'apply_material_to_actor' (applies), making its role unambiguous.

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

Usage Guidelines3/5

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

The description implies the tool is for listing materials, but does not provide explicit guidance on when to use this over alternatives (e.g., 'get_material_info' for details, 'search_material_functions' for functions). No exclusions or when-not-to-use are given.

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