Zovo Focus Timer

Show focus timer

show_focus_timer

Read-onlyIdempotent

Use this when the user wants a timer now: a pomodoro timer (25/5, 50/10, pomodoro timer for studying), a countdown timer ("10-minute timer"), or an interval timer (work/rest repeats, e.g. 45 s on, 15 s off). Returns the full phase plan (focus blocks, short and long breaks, totals) and shows a live timer with a progress ring, play, pause, skip and reset controls, and an optional chime. With a clock time for the first block and a time zone (IANA name such as Europe/Warsaw, a city, or an abbreviation such as EST), each phase also gets wall-clock times that stay correct across daylight-saving changes. Limits: up to 24 hours and 96 rounds; no phone notifications, alarms when the chat is closed, or music. Do not use for reminders about future appointments, questions about how long something takes (e.g. boiling an egg), or unit conversions.

Input Schema

Name	Required	Description
`date`	No	Optional date of start_time as YYYY-MM-DD, e.g. 2026-10-02. Defaults to today in time_zone.
`mode`	Yes	Timer type: "pomodoro" (focus blocks with short and long breaks, e.g. 25/5), "countdown" (one countdown, e.g. 10 minutes), or "interval" (repeating work/rest, e.g. 45 s on, 15 s off).
`label`	No	What the user is focusing on, shown on the timer, e.g. "Biology chapter 3" or "Presentation practice".
`sound`	No	Play a short chime when each phase ends. Default true.
`rounds`	No	Number of focus blocks, e.g. 4 (pomodoro default). Ignored for countdown.
`time_zone`	No	Optional time zone for start_time: an IANA name (e.g. Europe/Warsaw, America/New_York), a city (e.g. Warsaw), or an abbreviation (e.g. EST, CET). Makes the clock times correct across daylight-saving changes.
`start_time`	No	Optional clock time the session starts, as HH:MM (24-hour) or 9:30 am, e.g. 14:00. When given, every phase gets wall-clock start and end times.
`auto_advance`	No	Start the next phase automatically when one ends. Default true; false pauses after each phase until the user presses Start.
`work_minutes`	No	Length of each focus or work block in minutes, e.g. 25 for a classic pomodoro or 50 for 50/10. For countdown this is the countdown length, e.g. 10. Decimals allowed: 0.5 = 30 seconds. Default 25 for pomodoro.
`long_break_every`	No	Take the long break after this many blocks, e.g. 4 (pomodoro default). 0 = never.
`long_break_minutes`	No	Longer break taken after every long_break_every blocks, in minutes, e.g. 15 (pomodoro default).
`short_break_minutes`	No	Break between blocks in minutes, e.g. 5 (pomodoro default) or 10 for 50/10. For interval mode this is the rest, e.g. 0.25 = 15 seconds. 0 = no break.

Output Schema

Name	Required	Description	Default
`mode`	Yes
`label`	Yes
`notes`	Yes
`phases`	Yes
`totals`	Yes
`summary`	Yes
`schedule`	Yes
`settings`	Yes
`downloads`	Yes
`phase_count`	No
`spare_minutes`	Yes
`phases_truncated`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 22, 2026

TDQS

A3.8/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and non-destructive, so the safety profile is known. The description still adds real value beyond that: hard limits (24 hours, 96 rounds), what is NOT supported (phone notifications, alarms when chat is closed, music), and DST-correct wall-clock times when start_time and time_zone are supplied. It does not mention persistence of the timer between turns, which is the main remaining behavioral unknown for a live UI tool.

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?

Trigger is front-loaded in the first clause, followed by mode examples, then outputs, then limits and exclusions in a deliberate order. It is dense but each clause carries information; the parenthetical example stacks in the opening sentence slow scanning slightly.

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, a 12-parameter schema at full description coverage, and an output schema handling return shape, the description fills exactly the remaining gaps: when to call it, what the user sees, hard limits, unsupported capabilities, and time-zone behavior. Nothing an agent needs to invoke it correctly 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%, so every parameter is already documented in the schema, which sets the baseline at 3. The description adds behavioral meaning for the start_time/time_zone pairing (every phase gets wall-clock times that survive daylight-saving changes) but repeats the mode and break examples already present in the schema.

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 ('show a live timer' with progress ring, controls) and enumerates the three concrete timer modes, so an agent knows exactly what is produced. It does not name the sibling plan_focus_session, leaving differentiation to the implied 'timer now' framing.

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?

Opens with an explicit trigger ('when the user wants a timer now') and closes with three concrete exclusions: future appointment reminders, duration questions, and unit conversions. It never names plan_focus_session as the alternative for planning ahead, so sibling routing is only partially covered.

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

All Zovo Focus 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?