Skip to main content
Glama

Get the material palette

get_material_palette
Read-only

Material ids + keys + names + categories you can build with (146 entries; ids are SPARSE/non-contiguous, so always pass a returned key rather than guessing an id). Category names are specific (e.g. "natural-stone", "marble", "metal-(ferrous)", "emissive", "glass"), so the category arg is matched FORGIVINGLY - "stone" finds "natural-stone", "metal" finds "metal-(ferrous)". NOTE: the "glass" materials are fully OPAQUE (this world has no transparent material) - use them as tinted accent panels, never as see-through windows (a window is an empty hole, not a glass block). Call categories_only:true FIRST to see the exact category list, then drill down (keeps the payload small for a token-budgeted brain). Each entry carries a "look" field (e.g. "near-white polished marble with soft veining", "warm yellow-brown wood with visible grain") + an rgb + a colour word, so PICK BY APPEARANCE - choose materials whose look fits what you are making, and vary them across a structure (foundation vs walls vs roof vs trim) instead of one flat grey stone. You can pass any returned key (e.g. "calacatta-gold") straight to build/place_block material.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
styleNoReturn a style-keyed palette of 5 roles (foundation/wall/roof/trim/accent) for an architectural style. Known styles: korean-palace, french-baroque, roman-classical, japanese-zen, nordic-longhouse, desert-sandstone, fantasy-stone, modern-concrete. Unknown style returns {style:"unknown", hint}.
categoryNoReturn only materials in this category (case-insensitive).
categories_onlyNoReturn just the distinct category names + counts, no materials.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / additionalProperties
      Added value: +false
  2. First observed

TDQS

A4.7/5.0
Behavior5/5

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

Discloses beyond readOnlyHint: sparse non-contiguous ids, opaque glass materials, recommendation to vary materials. Annotations only indicate read-only, but description adds crucial behavioral details.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Long but efficient; every sentence adds value. Structure is clear: purpose, id/category tips, usage advice, appearance guidance. Could be slightly more concise, but not redundant.

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?

Given no output schema and 3 parameters, description is thorough: explains return format (look, rgb, colour word), usage patterns (pick by appearance, vary across structure), and integration with build tools. Complete.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Despite 100% schema coverage, description enriches each parameter: explains style returns 5 roles with known styles list, category matching is forgiving, categories_only returns counts. Adds significant value.

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 returns material ids, keys, names, and categories for building. It distinguishes itself from siblings like 'build' and 'place_block' by focusing on material selection, not block placement.

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

Usage Guidelines4/5

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

Provides explicit guidance: call categories_only:true first, use returned keys directly, explains forgiving category matching. Lacks explicit 'when not to use' but is otherwise clear.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources