Kitchen Timer

Add or take off time

adjust_dish

Add time to a dish (a positive number of minutes) or take time off (negative). Before the person taps Start this changes the plan, and the ready time stays; afterwards it changes that dish's timer 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>",
      "minutes": "<minutes>"
    },
    "name": "adjust_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).
`minutes`	Yes	Minutes to add (positive) or take off (negative), such as 2 or -1.5. Not zero.

Output Schema

Name	Required	Description	Default
`message`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 22, 2026

TDQS

A4/5.0

Behavior4/5

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

Annotations already declare non-read-only, non-idempotent, non-destructive behavior, and the description adds genuinely new operational context: pre-Start edits change the plan while preserving the ready time, post-Start edits change that dish's phone timer. That is real behavioral disclosure beyond the structured hints. It stops short of describing reversibility or error cases.

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 compact sentences, front-loaded with the action and sign convention, then the state-dependent effect. Every clause earns its place with no restatement of the title or schema.

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 all four required parameters are covered. The state-dependent semantics are captured, though permission/ownership requirements implied by the secret key are delegated entirely to the schema rather than the description.

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%, so the baseline of 3 applies. The description's only parameter-level contribution is restating that minutes are positive to add and negative to remove, which the schema already documents with range and a 'not zero' constraint. It adds no format or syntax detail beyond the schema.

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 (adjust/add or remove time) and resource (a dish's time) in the first clause, with the sign convention defined inline. No sibling tool (skip_step, pause_meal, cancel_meal) performs a per-dish time adjustment, so the agent can disambiguate immediately.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies usage through the before/after-Start distinction, which tells the agent the tool is valid in both plan and running states. However, it never states when to prefer this over siblings like skip_step or plan_meal, nor any exclusions or prerequisites beyond the required code/key.

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?