Skip to main content
Glama

Cabinet wood and hardware finishes

list_finishes
Read-onlyIdempotent

Cabinet wood and hardware finish options for visualize_kitchen and generate_quote. Visualization only: ATX Granite King installs countertops, not cabinets or hardware. 'keep' (default) keeps the user's own.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent and non-destructive, so safety is covered. The description adds real domain context — visualization-only scope and that 'keep' (default) preserves the user's own finish — but the mention of a 'keep' default is confusing for a tool with zero parameters, since nothing indicates whether it is a returned option or an input.

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?

Three short sentences, front-loaded with the resource and its consumers, followed by the scope caveat. Every sentence carries information, with only the 'keep' (default) clause being underspecified relative to its length.

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?

There is no output schema, so the description should hint at the return shape — a list of finish names/IDs meant to be passed into visualize_kitchen or generate_quote — and it doesn't. The scope exclusion is good, but an agent still doesn't know how to use the results.

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?

The tool takes no parameters, so the baseline is 4. The description correctly spends no words on inputs, though it does introduce the 'keep' value without clarifying where it appears.

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 the resource precisely (cabinet wood and hardware finishes) and binds it to the two consumer tools, visualize_kitchen and generate_quote, which separates it from stone/pricing siblings. It lacks an explicit verb ('list'), so the read behavior is only implied by the name.

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?

It clearly says the tool exists to supply finish options to visualize_kitchen and generate_quote, and adds a firm exclusion: the business installs countertops, not cabinets or hardware, so this is visualization-only. It stops short of stating when an agent should skip calling it (e.g., if the user is only pricing countertops).

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