Skip to main content
Glama

Little Works

list_materials

Catalog specialty materials by trade (exterior, plumbing, HVAC, electrical, tile, hardware).

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
tradeNoTrade slug: exterior|plumbing|hvac|electrical|tile|hardware

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full burden. It implies a read-only catalog via the word "Catalog" but says nothing about permissions, pagination, result size, or what a material record contains — all of which an agent would need to plan a call.

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?

A single front-loaded sentence with zero filler, and the trade scoping is stated immediately. The parenthetical value list is somewhat redundant with the schema but not wasteful enough to hurt.

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 one-parameter read tool with no annotations and no output schema, the definition is minimally adequate. It never indicates whether trade is optional or what happens when it is omitted, nor what the response shape is, which leaves real gaps for a browsing call.

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% and the single `trade` parameter is already documented with its allowed slugs. The description restates the same six trade values but adds no meaning beyond the schema, so the baseline 3 applies.

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 gives a specific verb ("Catalog") and resource ("specialty materials") plus the organizing dimension (trade), so an agent knows exactly what it returns. It does not, however, distinguish itself from siblings like search_materials or list_materials_places, leaving the boundary to inference.

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

Usage Guidelines2/5

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

There is no when-to-use guidance and no named alternative, despite search_materials and list_materials_places existing in the same family. The only signal is the implicit notion that this is a browsing/catalog call rather than a targeted lookup.

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