Skip to main content
Glama
Sign In
MCPBridge Server

MCPBridge Server

by RBG-WebDesign
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

material_list

Lists materials in an Unreal Engine project, allowing filtering by path, name, and type to locate specific assets.

Instructions

List materials in the project with optional filtering by path, name, and type.

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

Input Schema

NameRequiredDescriptionDefault
limitNoMax results to return
name_filterNoFilter by material name (supports fnmatch wildcards)
path_filterNoContent path prefix filter (default /Game/)
type_filterNoFilter by material typeall

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

A3.5/5.0
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It only says 'List materials' and does not explicitly state that this is a read-only operation, nor does it mention any side effects, permissions, pagination, or defaults. The absence of such details leaves significant uncertainty for an agent deciding whether to invoke this 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?

The description is a single, well-structured sentence with no redundant words. It front-loads the action ('List materials') and immediately mentions the optional filters, making it easy to parse and understand.

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?

For a simple listing tool with four optional parameters and no output schema, the description is minimally adequate. It tells the agent what the tool does but does not mention the default limit, default path prefix, or return format. Given the absence of annotations and output schema, a bit more context (e.g., that it returns material paths or includes only assets under /Game/) would improve completeness.

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?

The schema provides 100% coverage of all four parameters, each with descriptive text. The description merely repeats the filter names (path, name, type) without adding extra meaning about wildcard behavior, default values, or how filters interact. This meets the baseline for high schema coverage but adds no additional insight.

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 the tool's function: 'List materials in the project' with a specific verb and resource. It also mentions the filtering dimensions (path, name, type), which distinguishes it from sibling tools like material_info (which likely fetches a single material) and material_create (which creates a material).

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 used to enumerate materials, especially when filtering is needed, but it does not explicitly contrast it with sibling tools like asset_list or material_info. No 'when to use' or 'instead of' guidance is provided, so the usage context is only implied.

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