Skip to main content
Glama
Kitchen Pass MCP server

Kitchen Pass MCP server

Official

What Kitchen Pass answers (free)

check_coverage
Read-onlyIdempotent

Lists covered dishes, symptoms, ingredients, swaps, techniques, and topics so you can check support before calling a paid tool. Fetch one section or the full coverage list.

Instructions

Free. Lists by name everything the paid Kitchen Pass tools answer today: diagnose dishes with their symptom wordings, ingredients with answered swaps, yield ingredients with aliases (used by both calculate_yield_and_cost and calculate_amount_to_buy), scaling classes and tip topics, gluten-free flours, starters, swaps, techniques, problem wordings and recipes, and the food-safety topics that are always refused. Names only, never the answers. Call it before a paid tool when unsure whether a dish, symptom or ingredient is covered. Use section to fetch one part only.

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": "check_coverage"
  }
}

Input Schema

NameRequiredDescriptionDefault
sectionNoReturn one part of the list only.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4/5.0
Behavior4/5

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

Annotations already establish readOnly, idempotent and openWorld, so the safety profile is covered. The description adds genuinely useful behavior the annotations cannot convey: the response is 'Names only, never the answers,' and certain food-safety topics are always refused. It does not say how large the list is or whether it is bounded, which keeps it off a 5.

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

Conciseness3/5

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

The key facts are front-loaded ('Free.' then the coverage statement), but the middle collapses a dozen distinct categories into one run-on sentence that is hard to parse. The content largely earns its place, yet a short list structure would convey the same scope more clearly in less space.

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 read-only index tool with no output schema and fully documented parameters, the description covers purpose, when to call it, what the return contains, and the refusal behavior. It is close to complete; the only notable omission is any sense of result size or whether the full list is returned in one call.

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?

Schema coverage is 100% and the single enum parameter already carries a description ('Return one part of the list only'). The description's 'Use section to fetch one part only' restates that almost verbatim, adding no meaning about the six enum values or what each section contains. Baseline 3 applies since the schema does the work.

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: it 'lists by name everything the paid Kitchen Pass tools answer.' The enumeration of covered categories makes the scope concrete, and the contrast with 'the paid Kitchen Pass tools' plus the note about food-safety topics that are 'always refused' distinguishes it from the answer-returning siblings without opening their schemas.

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?

Gives an explicit trigger: 'Call it before a paid tool when unsure whether a dish, symptom or ingredient is covered,' which names both the situation and the alternatives (the paid tools). It also explains the narrowing case for `section`. It stops short of stating when not to bother calling it (e.g. when coverage is already known), so it is clear context rather than full when/when-not guidance.

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