Skip to main content
Glama

NewKitchenAI - Kitchen Design Reference

NewKitchenAI capabilities and limits

get_product_info
Read-onlyIdempotent

Get photo-based kitchen design capabilities, payment requirements, limitations and official website links. Does not generate images.

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

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=true, idempotentHint=true, non-destructive and closed-world, so the safety profile is covered. The description adds that output is informational (capabilities, payment requirements, limitations, links) and clarifies what the tool does NOT do. It does not disclose return format or detail level, but with annotations carrying the behavior burden this is adequate.

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?

Two compact sentences, front-loaded with the resource and followed by the key exclusion. No filler; the exclusion clause earns its place by preventing a misinvocation.

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 zero-parameter informational tool with no output schema, the description covers what content is returned at a high level and what it does not do. It could be stronger by stating that it returns static reference/policy information rather than per-project data, which is the main ambiguity against pricing and materials siblings.

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?

The tool takes zero parameters, so the baseline is 4 per the rubric; however the description adds no parameter context because none exists. A 3 reflects that nothing beyond the empty schema needed explaining, and the description spends its words on scope instead.

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 states a specific resource ('photo-based kitchen design capabilities, payment requirements, limitations and official website links') with a clear verb 'Get', and explicitly excludes image generation. The negative scope ('Does not generate images') helps distinguish it from design tools, though the sibling tools listed (materials, styles, examples, pricing) aren't directly differentiated beyond the exclusion.

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

Usage Guidelines3/5

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

The exclusion 'Does not generate images' implies usage boundaries, and the content list hints at when this informational tool is appropriate. However, it never explicitly says when to call this versus get_pricing or get_kitchen_materials, so the agent must infer the routing.

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.