Kitchen Timer

Add a dish to the plan

add_dish

Add one more dish to this plan. The ready time stays, so the new dish goes in at the ready time minus its cooking time and must still fit. Before the person taps Start it joins the plan on the sheet; afterwards it goes onto the phone too. Same rules as plan_meal: a plain-text name, at most 12 dishes. 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>",
      "name": "<name>",
      "minutes": "<minutes>"
    },
    "name": "add_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.
`name`	Yes	Plain text, 80 characters at most.
`steps`	No	Optional moments inside the cooking time.
`minutes`	Yes	Total cooking time in minutes.

Output Schema

Name	Required	Description	Default
`message`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 22, 2026

TDQS

A4.3/5.0

Behavior5/5

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

Goes well beyond the annotations (write, non-idempotent, non-destructive): it discloses that the ready time is preserved, that the dish lands at ready-time minus cooking time and must still fit, and that the write propagates to the phone only after Start. It also states the control-key requirement, which is real auth context.

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?

Four short sentences, front-loaded with purpose and each earning its place by adding a rule. The closing 'Needs the plan's code and control key' mildly repeats what the schema already describes, a small redundancy.

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?

With annotations covering safety and an output schema covering returns, the description supplies what remains: add semantics, timing math, the 12-dish cap, and pre/post-Start propagation. An agent has everything needed to invoke it correctly.

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 cross-field meaning not in the schema: 'plain-text name, at most 12 dishes' and the timing rule tying minutes to the ready time. These are constraints the schema alone does not express.

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 and resource ('Add one more dish to this plan') and distinguishes itself from plan_meal by implying the plan already exists. It never names a competing sibling (e.g. adjust_dish) as the alternative for modifying an existing dish, so differentiation is inferential rather than explicit.

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?

Clear context: it belongs to an existing plan, and the before/after Start branching tells the agent when its effect differs. It references plan_meal for shared rules but does not state when NOT to use it or which sibling to prefer for related edits.

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?