Skip to main content
Glama

NewKitchenAI - Kitchen Design Reference

Kitchen remodel and refinement examples

get_design_examples
Read-onlyIdempotent

Get existing and unfinished kitchen before/after examples, plus a cabinet-color and countertop refinement sequence.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

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, openWorldHint=false and destructiveHint=false, so safety behavior is covered. The description does add real context beyond the annotations: some examples are "unfinished," and there is an ordered "refinement sequence" for cabinet color and countertop, which signals a progression rather than a flat list. It stops short of saying what is actually returned (images, URLs, text specs), which matters given no output schema.

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

Conciseness5/5

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

One sentence, front-loaded with the verb and the primary content, and every clause adds a distinct piece of information (existing vs unfinished examples, then the refinement sequence). There is no filler or restatement of the title.

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?

With zero parameters, full annotation coverage and no output schema, the description carries the burden of explaining the returned content, and it only gestures at it ("before/after examples," "refinement sequence"). An agent knows roughly what domain this covers but not what form the payload takes or how the sequence is ordered.

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 zero parameters, so there is nothing for the description to disambiguate at the input level; baseline 4 applies. No misleading parameter talk is present.

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 concrete verb ("Get") and a concrete resource (kitchen before/after examples, plus a cabinet-color and countertop refinement sequence). That is much more specific than the title alone, though it never contrasts itself with siblings such as get_kitchen_materials or list_kitchen_styles, so the boundary between "examples" and "materials/styles" must be inferred.

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 explicit when-to-use or when-not-to-use guidance, and no alternative tool is named. The agent can only guess that this is the inspiration/reference tool versus the catalog-style siblings, because nothing in the text states the condition that should select it.

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.