Skip to main content
Glama

List materials and colors

list_materials
Read-onlyIdempotent

Materials, finishes, strengths and colors the Printlooper print shops offer, with how many shops offer each. Filter colors by material, finish or color family.

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

Input Schema

NameRequiredDescriptionDefault
finishNo
materialNo
color_familyNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so the safety profile is covered. The description adds genuinely useful behavior — results are aggregated with per-shop counts — but leaves open whether the catalog is global or scoped to the caller's shops, and says nothing about result shape or paging.

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?

Two short sentences with no filler, and the what-it-returns information is front-loaded ahead of the filtering note. The opening is a noun fragment rather than a verb phrase, which slightly weakens the lead.

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 read-only list tool this covers the essentials, but with no output schema and zero schema-level parameter documentation, the definition should say more about the returned fields and valid filter values. The ambiguity about global versus shop-scoped data is a real gap an agent would hit.

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 description must carry the parameters, and it does identify the three filter dimensions by name and ties them to color filtering. However it is ambiguous whether material also filters the material list itself, and it gives no expected value formats or examples for any of the three string parameters.

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?

The description names a specific resource set (materials, finishes, strengths, colors offered by Printlooper print shops) and states the aggregation ('how many shops offer each'), which is enough to tell it apart from the add_* catalog siblings. It stops short of explicitly contrasting itself with any named sibling.

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 second sentence explains how the three filters narrow the color results, which gives implied usage context. There is no statement of when to prefer this over alternatives such as add_material_colors or list_print_shops, and no exclusions.

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