Skip to main content
Glama
Kitchen Pass MCP server

Kitchen Pass MCP server

Official

Free sample answer (demo only)

get_sample_answer
Read-onlyIdempotent

Fetch a fixed demo bread recipe scaled from 10 to 60 portions to preview the structure of a paid cooking answer before asking your own question.

Instructions

Free. A fixed demo: one bread recipe scaled from 10 to 60 portions by the same engine as scale_recipe. It does not answer the user's question; use it only to see the shape of a paid answer.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and openWorldHint, so the safety profile is covered. The description adds genuine context beyond that: the payload is fixed and deterministic, is a demo of a paid product, and is not a query-responsive answer. It stops short of describing the response shape, but names it as 'the shape of a paid answer', which is enough orientation for a zero-param demo.

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 'Free.' and the demo caveat. Every clause carries information: cost, what it returns, how it was produced, and what it is not for.

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

Completeness5/5

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

For a zero-input, no-output-schema demo tool, nothing material is omitted. Cost, fixedness, provenance, and misuse warning are all present, and the annotations already cover the read-only and idempotency questions.

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?

Zero parameters, so there is nothing for the description to disambiguate; the baseline for a parameterless tool applies. Calling the description out for missing parameter detail would be unfair.

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?

States a specific verb and resource: returns a fixed demo answer, one bread recipe scaled from 10 to 60 portions. It explicitly distinguishes itself from scale_recipe by saying the demo was produced by 'the same engine as scale_recipe', so an agent can place it relative to a sibling without opening schemas.

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

Usage Guidelines5/5

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

Gives both the when and the when-not: 'use it only to see the shape of a paid answer' versus 'It does not answer the user's question.' The exclusion is explicit, so an agent knows not to route real recipe-scaling requests here.

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