Skip to main content
Glama

Material List

material_list
Read-only

List available materials, optionally filtered by category such as aluminum, steel, or polymer, and return sorted names for selecting design materials.

Instructions

List available materials, optionally filtered to one category ('aluminum' | 'steel' | 'titanium' | 'magnesium' | 'polymer' | 'glass'). Returns {count, category, materials:[{name, category}, ...]} sorted by name.

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
categoryNo
workspaceNoRun this call in this named workspace

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.5.7
    • addedInput schema / properties / workspace
      Added value: +{
      +  "default": "",
      +  "description": "Run this call in this named workspace",
      +  "title": "Workspace",
      +  "type": "string"
      +}
  2. First observed

TDQS

A3.9/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, so the safety profile is covered. The description adds real value beyond that by disclosing the return payload shape and the sort order ('sorted by name'), which an agent cannot get from annotations. It stops short of noting error behavior for an invalid category.

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?

Two sentences, zero waste: the operation and optional filter come first, then the return shape. Every clause carries information the agent needs.

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?

With no output schema, the description correctly supplies the return structure and sort order, and it fills the undocumented category parameter. Only minor gaps remain, such as behavior on an unrecognized category value or how workspace scopes the listing.

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 only 50% and the category parameter carries no description or enum in the schema, so the description's inline enumeration of 'aluminum' | 'steel' | 'titanium' | 'magnesium' | 'polymer' | 'glass' is essential and materially compensates for the gap. The workspace parameter is left to the schema, which does document it.

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 specific verb and resource ('List available materials') plus the optional category filter and its exact allowed values. It does not explicitly distinguish itself from near-siblings like material_get or material_select, but the scope (enumerate all, not fetch one) is inferable from 'List'.

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 phrase 'optionally filtered to one category' implies when to pass the filter versus omitting it, but there is no explicit guidance on when to use this versus material_get, material_select, or catalog_search. Usage is implied rather than stated.

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