Skip to main content
Glama

NewKitchenAI - Kitchen Design Reference

Kitchen materials and lighting options

get_kitchen_materials
Read-onlyIdempotent

Look up cabinet finishes, countertops, backsplash, flooring, lighting and kitchen element options in the website tool.

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": "get_kitchen_materials"
  }
}

Input Schema

NameRequiredDescriptionDefault
categoryNo

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?

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and closed-world scope, so the safety profile is covered. The description adds nothing beyond that – no statement of return shape, whether omitting the category returns all options, or whether results are pricing-free (relevant since get_pricing is a sibling).

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?

One sentence, verb-first, no padding around the resource list. The trailing 'in the website tool' is the only vaguely unearned wording and adds ambiguity rather than information.

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 lookup with one optional enum parameter and full annotation coverage, this is close to sufficient. Missing default-behavior disclosure (no category = all categories?) and any hint at result format leaves a small but real gap.

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%, but the single parameter is an enum whose six values the description enumerates, so an agent can infer valid inputs from the prose. It still omits the key semantic point that the parameter is optional and what happens when it is omitted.

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?

Clear verb ('Look up') plus an explicit enumeration of resources (cabinet finishes, countertops, backsplash, flooring, lighting, kitchen elements) that maps directly onto the tool's domain. It does not, however, distinguish this from plausible siblings like get_design_examples or get_product_info, so an agent must guess which retrieval tool to pick.

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?

No when-to-use, when-not-to-use, or alternative routing is given; the definition never names another tool or a selection condition. The phrase 'in the website tool' is a location hint, not guidance on choosing this over get_design_examples.

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.