Skip to main content
Glama

NewKitchenAI - Kitchen Design Reference

NewKitchenAI pricing

get_pricing
Read-onlyIdempotent

Read official one-time credit-pack prices and usage rules. Reads the website with a dated fallback if unavailable. Does not purchase or charge credits.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, so the safety profile is covered. The description adds genuinely new behavior: it reads the live website and falls back to a dated snapshot when unavailable, which tells the agent results may be stale and are timestamped. It does not state rate limits or how the dating is surfaced, keeping it below the top mark.

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?

Three short sentences, front-loaded with the core purpose, then the fallback caveat, then the exclusion. No sentence is filler and nothing important is buried.

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, side-effect-free lookup with no output schema, the definition covers purpose, sourcing, fallback behavior and scope limits. The only gap is the shape of the returned price/rule data, which the agent must discover at call time.

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 there is nothing for the description to disambiguate; the 4 baseline applies. The mention of a dated fallback is the only adjacent detail and is not a parameter concern.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

"Read official one-time credit-pack prices and usage rules" gives a specific verb (read) and a precisely scoped resource (credit-pack pricing plus usage rules). It is immediately distinguishable from siblings like get_product_info or get_kitchen_materials, which cover catalog/material data rather than pricing.

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?

The definition makes the use case clear (fetch authoritative prices before quoting them) and explicitly bounds it with "Does not purchase or charge credits," which prevents an agent from mistaking it for a purchase flow. It stops short of naming an alternative channel for transactions, so it is clear context rather than a full when/when-not routing rule.

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.