Kitchen Timer

Start a dish after another dish

link_dish

Make a dish start a while after another dish goes in or is done ("the potatoes 30 minutes after the chicken goes in"), or clear that link by leaving after out. Starting the other dish early or late then moves this one with it. A dish cannot wait on a dish that waits on it, and a dish that already started cannot be linked. 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": "link_dish"
  }
}

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).
`when`	No	Count from when that dish goes in, or from when it is done.
`after`	No	The dish to follow: its name as in the plan, or its number. Leave out to clear this dish's link.
`minutes`	No	Minutes after that moment. 0 or left out: right then.

Output Schema

Name	Required	Description	Default
`message`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 27, 2026

TDQS

A4.5/5.0

Behavior5/5

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

Goes well beyond annotations: it explains the cascading behavior (moving the anchor moves this dish), states two hard constraints (no circular waits, cannot link an already-started dish), and notes the required credentials. That is meaningful behavior not conveyed by the readOnly/idempotent hints.

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

Conciseness4/5

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

Front-loaded with the core action and an example, then constraints. Dense but every sentence carries information; the parenthetical example costs a little space but aids comprehension.

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 6-parameter mutation tool with an output schema and full schema coverage, the description covers purpose, constraints, credential needs, and clearing behavior. Only the absence of explicit sibling routing keeps it short of perfect.

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?

Schema coverage is 100%, so the baseline is 3, but the description adds real semantics: 'leaving `after` out' clears the link, and 'a while after... goes in or is done' clarifies the when/minutes relationship. It also reinforces that code and key are needed.

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 (link a dish to start after another) with a concrete example and explicitly covers the clear-link variant. It is clearly distinguishable from siblings like add_dish, adjust_dish, or skip_step.

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 description gives a vivid when-to-use example and explains the clear-link case via omitting `after`, but it never names an alternative tool or states when another tool (e.g., adjust_dish) would be the right choice instead.

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?