Material Maker MCP

Overview Schema Source Related Servers Discussions Admin

list_material_recipes

Read-onlyIdempotent

Fetch curated declarative starter recipes for Material Maker, filtered by tag or query, to find a reusable procedural material graph.

Instructions

List the curated declarative starter recipes, optionally filtered by text or tag.

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_material_recipes"
  }
}

Input Schema

Name	Required	Description	Default
`tag`	No
`query`	No

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.3.1Sep 29, 2026

TDQS

A3.6/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered. The description adds only the 'curated declarative starter recipes' framing, with no detail on result ordering, limits, or pagination, so it earns a baseline 3 rather than more.

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?

A single front-loaded sentence with the resource named first and the optional filtering clause trailing. Zero wasted words.

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-value description is unnecessary, and annotations cover the safety profile. For a two-param list tool the description is nearly complete, lacking only filter semantics.

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%, so the schema titles ('Tag', 'Query') carry little meaning. The description compensates by mapping the filters to text and tag, but it gives no matching semantics (substring vs exact, tag vocabulary) and no note that both are optional with empty-string defaults.

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 clear verb+resource ('List ... recipes') with the qualifier 'curated declarative starter recipes', which distinguishes it from the sibling describe_material_recipe and apply_material_recipe. It doesn't explicitly name those siblings, so it stops short of a 5.

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?

'Optionally filtered by text or tag' implies how to narrow results, but there is no statement of when to use this versus describe_material_recipe or apply_material_recipe. Usage is implied rather than prescribed.

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