Skip to main content
Glama

search_materials

Read-only

Lists custom MaterialVariants in a place's MaterialService with their base materials, helping you find material names to apply to parts via set_property or mass_edit.

Instructions

List the custom MaterialVariants defined in this place's MaterialService, with each one's base material. Read-only. Use it to find a material name to set on parts with set_property or mass_edit. For marketplace assets use search_assets; for other instances use search_objects.

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

Input Schema

NameRequiredDescriptionDefault
nameNoOnly list variants whose name contains this text. Omit to list all.
placeNoTarget place (PlaceId or project name). Defaults to the bound/sole connected place.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.1.1
    • changedInput schema / properties / name / description
      Previous value: -"filter by name substring"New value: +"Only list variants whose name contains this text. Omit to list all."
  2. First observedv0.1.0

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, and the description restates read-only, which is mildly redundant. It does add value beyond the annotations by disclosing scope (custom variants only, implicitly excluding built-in materials) and return content (each variant's base material). It stops short of noting result size, ordering, or whether built-in materials appear.

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 with no filler: purpose and scope first, then the concrete use, then the disambiguation. Every clause carries information an agent needs to pick or call the tool.

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

Completeness5/5

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

For a simple two-parameter read tool with a fully described schema and no output schema, the description covers what it returns (variants plus base material), where it reads from, and how it relates to sibling searches. Nothing needed for correct invocation is missing.

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 coverage is 100%, so both parameters (name substring filter and place target) are already fully documented in the schema. The description adds no syntax, format, or matching-behavior detail beyond that, so the baseline 3 applies.

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?

States a specific verb and resource (list the custom MaterialVariants) plus scope (in this place's MaterialService) and what accompanies each result (its base material). The agent can distinguish this from search_assets and search_objects without opening any schema.

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

Usage Guidelines5/5

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

Gives a concrete downstream use case (finding a material name to pass to set_property or mass_edit) and names both alternatives with the condition that selects them: search_assets for marketplace assets, search_objects for other instances. When-to-use and when-not-to-use are both explicit.

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