Kitchen Timer

Cancel the meal

cancel_meal

Destructive

Cancel this plan: its link stops working, and if the person already started it, its timers are removed from the phone. Only that plan's timers; nothing else on the phone. Needs the plan's code and control key. Ask the person first.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "code": "<code>",
      "key": "<key>"
    },
    "name": "cancel_meal"
  }
}

Input Schema

Name	Required	Description	Default
`key`	Yes	The secret control key plan_meal gave you for this plan (starts with ktpk_). Never show it or put it in a link.
`code`	Yes	The plan's code, or its whole link.

Output Schema

Name	Required	Description	Default
`message`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 22, 2026

TDQS

A4.1/5.0

Behavior5/5

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

Annotations only say destructiveHint=true and non-idempotent; the description adds the exact blast radius (only that plan's timers, nothing else on the phone), what state changes (the link stops working), and a confirmation requirement. That is materially more than the annotations convey.

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?

Two tight sentences, front-loaded with the effect of cancellation before the prerequisites and the caution. Every clause carries information — scope, side effects, required inputs, confirmation.

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?

With an output schema present, return values need no explanation, and annotations carry the safety profile; the description covers prerequisites, scope, and confirmation. It stops short of stating whether cancellation is irreversible or recoverable, which matters for an agent choosing between cancel and pause.

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 description coverage is 100% and the schema itself explains that key is a ktpk_ secret that must never be shown and that code may be a code or full link. The description merely restates that both are needed, adding no meaning beyond the schema; baseline 3 applies.

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?

States a specific verb (cancel) and resource (this plan) and spells out the concrete consequences: the link stops working and the plan's timers are removed from the phone. That behavioral detail implicitly separates it from pause_meal/resume_meal, but no sibling is named, so it falls just short of the top band.

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 real invocation context — it requires the plan's code and control key, and instructs the caller to 'ask the person first' before cancelling. It does not explicitly contrast cancel against pause_meal or resume_meal, so the when-not-to-use case is left to inference.

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

All Kitchen Timer tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?