Eggtimer.app

Create a recipe link

create_recipe

Read-onlyIdempotent

Validate a data-only recipe and return its portable preview link. The person opens it and presses Start. No code runs and no webhook is armed.

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": {
      "recipe": "<recipe>"
    },
    "name": "create_recipe"
  }
}

Input Schema

Name	Required	Description	Default
`recipe`	Yes	Recipe v1: 1–12 whole-second steps, no repeats. v2: 1–32 steps, fractional seconds and repeats. At most 512 expanded intervals and 10 years; defaults may be omitted.

Output Schema

Name	Required	Description	Default
`url`	Yes
`recipe`	Yes
`intervals`	Yes
`start_behavior`	Yes
`duration_seconds`	Yes
`integration_note`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 18, 2026

TDQS

A3.8/5.0

Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), so the bar is lower. The description still adds real value by clarifying that the output is a shareable link the user must activate manually and that no code executes and no webhook is armed — a non-obvious trait given the schema's completion.webhook flag. It does not disclose validation-failure behavior or link persistence/lifetime.

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?

Three short sentences, front-loading the action and return value, then the user flow, then the negative constraint. Zero filler and nothing repeated from the 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 details need not be explained, and the description covers validation and the no-code/no-webhook constraint for a single-object parameter. Minor gaps remain around what a validation failure returns, but nothing essential for correct invocation is missing.

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 nested recipe schema is extensively self-documenting (version rules, step/intervals limits, theme colors), so the schema carries the parameter burden. The description adds only the 'data-only recipe' framing and nothing about step or version semantics, matching the baseline 3.

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?

Names a specific action (validate a recipe and return its portable preview link) on a specific resource, and the phrase 'data-only recipe' plus 'preview link' distinguishes it from the timer/clock-link siblings. It stops short of explicitly naming an alternative, so sibling differentiation is inferred rather than stated.

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?

Implies the intended flow ('The person opens it and presses Start') and implicitly rules out webhook/automation use ('no webhook is armed'), which is useful context. However, there is no explicit when-to-use vs. when-not guidance nor any reference to the sibling tools an agent might pick instead, so usage is only implied.

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

All Eggtimer.app 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?