Skip to main content
Glama
NewKitchenAI MCP

NewKitchenAI MCP

by weiwosuoai

Kitchen style catalog

list_kitchen_styles
Read-onlyIdempotent

List available kitchen design styles and preview-image links from NewKitchenAI to help users choose a remodel style.

Instructions

List the kitchen design styles and preview-image links available on NewKitchenAI.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.1

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, destructiveHint=false, and closed-world scope, so the safety profile is covered structurally. The description adds useful context that results include preview-image links, which the annotations do not convey. It omits pagination or ordering behavior, but that is minor for a static catalog.

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 efficient sentence with the main purpose front-loaded and zero filler. It could squeeze in slightly more return-value detail but is appropriately sized for a trivial catalog read.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a zero-parameter, read-only catalog tool with full annotation coverage and no output schema, the description is largely sufficient. The only missing nuance is the shape of the returned links, a minor gap.

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 schema description burden is nil; baseline 4 applies. The description does not need to explain any input semantics.

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?

Specific verb 'List' with concrete resources: kitchen design styles and preview-image links, on the named platform NewKitchenAI. It does not explicitly distinguish itself from siblings like get_design_examples, but the resource is stated clearly enough that an agent can identify it as a style catalog.

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 guidance on when to use this tool versus alternatives such as get_design_examples, and no exclusions or preconditions. Usage is only implied by the phrase 'available on NewKitchenAI'.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.