Eggtimer.app

Create a timer link

create_timer

Read-onlyIdempotent

Validate a duration and return a link. The countdown starts when the person opens it, not when this tool runs. No background alarm or automation is scheduled.

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": {
      "duration": "<duration>"
    },
    "name": "create_timer"
  }
}

Input Schema

Name	Required	Description
`label`	No	Omit unless requested.
`muted`	No	Omit to use defaults.
`theme`	No	Omit to use defaults.
`display`	No	Omit to use defaults.
`duration`	Yes	Relative duration, e.g. 12m or 1h20m. Bare numbers mean minutes. Use recipes for sequences.

Output Schema

Name	Required	Description	Default
`url`	Yes
`alarm_note`	Yes
`start_behavior`	Yes
`duration_seconds`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 18, 2026

TDQS

B3.1/5.0

Behavior4/5

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

Annotations already establish readOnly/ non-destructive / idempotent, so the safety profile is covered. The description adds genuinely new behavioral facts the schema cannot express: the countdown starts on link open rather than at tool execution, and no background alarm or automation is scheduled. It does not cover link expiry or response shape, but the added scheduling semantics are substantive.

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?

Three short sentences with no filler, and the key non-obvious fact (countdown starts on open, not on execution) is stated early. The opening 'Validate a duration and return a link' is slightly misleading as a lead, costing a point.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/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 annotations cover safety. However, nothing addresses selection against the six sibling tools or lifecycle details such as whether the generated link expires, leaving a real gap for a tool whose whole output is a link.

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%, including duration format examples and enum values, so the structured fields already carry the parameter meaning. The description only adds 'validate a duration,' which implies invalid formats are rejected but adds no syntax or constraint detail beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description frames the tool as 'Validate a duration and return a link,' which describes an implementation step rather than the user-facing outcome (creating a shareable countdown timer). The resource is implied only via the name and title, and nothing distinguishes it from the sibling create_clock_link, which an agent must choose between.

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

Usage Guidelines2/5

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

There is no guidance on when to pick this over create_clock_link (target time vs. relative duration) or create_recipe (sequences), even though the duration description hints that 'recipes' exist for sequences. The agent is left to infer selection from sibling names alone.

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?