Kitchen Timer

Skip ahead on a dish

skip_step

Skip the rest of the current wait for one dish: a dish still waiting to go in starts now, and a dish that is cooking finishes now. Only works after the person has tapped Start on the phone. Needs the plan's code and control key.

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>",
      "dish": "<dish>"
    },
    "name": "skip_step"
  }
}

Input Schema

Name	Required	Description
`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.
`dish`	Yes	The dish's name as in the plan, or its number in the plan (1 is the first dish).

Output Schema

Name	Required	Description	Default
`message`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 22, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already declare readOnly=false, idempotent=false, destructive=false, openWorld=false, so the safety profile is covered. The description adds real context beyond that: exactly what state change occurs for each dish state and the sequencing precondition, which is what an agent needs to predict the effect.

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 action and its two outcomes before the precondition. Every clause carries information; nothing is redundant.

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 not be explained, and the description covers preconditions, both state branches, and required credentials. Minor gap: it does not state what happens on failure (e.g., calling before Start), though 'Only works after' implies rejection.

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%, so the schema already documents code, key, and dish in full detail (including the ktpk_ prefix and secret-handling warning). The description's 'Needs the plan's code and control key' repeats that requirement without adding format or syntax value, so baseline 3 applies.

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 ('skip the rest of the current wait') scoped to one dish, and enumerates the two distinct outcomes for a waiting dish vs a cooking dish. An agent can distinguish this from adjust_dish or pause_meal without opening a schema.

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 a clear precondition ('Only works after the person has tapped Start on the phone') and describes the behavioral trigger, so the agent knows when the call is valid. It does not name alternative siblings for adjacent goals, so it stops short of a 5.

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?