Skip to main content
Glama
julanbasnet

timermcp

by julanbasnet

Configure TimerMCP

timer_config
Idempotent

Configure TimerMCP settings: announcement style, latency handicaps, runaway timer limit, and cloud sync. Read current config by calling without arguments.

Instructions

Read or update TimerMCP settings. Call with no args to read.

Settings:

  • announcer ('hype'|'zen'|'sergeant'|'sports'|'minimal'): Default announcement personality. Styles: hype, zen, sergeant, sports, minimal.

  • start_offset_ms / stop_offset_ms (number ≥ 0): Latency handicaps subtracted from every elapsed. Leave at 0 for most uses — symmetric pipeline latency already cancels because both timestamps are taken server-side on a monotonic clock. Set these only to bias out a known asymmetry (e.g. user reckons their "stop" reaches the server ~300ms slower than their "start").

  • max_hours (number): A running timer older than this is flagged runaway (default 4).

  • sync_token (string): Enables cloud auto-sync. The user gets this token from their dashboard at https://timermcp.vercel.app/app ("set my timer sync token to …"). Every finished run then syncs automatically. Pass an empty string to disable sync.

  • sync_url (string): Override the cloud endpoint (default https://timermcp.vercel.app).

Returns: { config: {announcer, start_offset_ms, stop_offset_ms, max_hours, sync_enabled, sync_token_tail?, sync_url?}, dashboard_url, data_dir }

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sync_urlNoCloud sync endpoint override
announcerNoDefault announcement personality
max_hoursNoHours before a running timer is flagged runaway
sync_tokenNoCloud sync token from the TimerMCP dashboard; empty string disables sync
stop_offset_msNoDefault stop-side handicap in ms
start_offset_msNoDefault start-side handicap in ms

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
configYes
data_dirYes
dashboard_urlYes
Behavior4/5

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

Annotations indicate idempotent and non-destructive. Description adds detailed behavior: sync token enables sync, max_hours flags runaways, pipeline latency cancellation explained. No hidden effects mentioned.

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?

Well-structured with bullet points, front-loaded purpose. Slightly lengthy but every sentence adds value; no unnecessary repetition.

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?

Complete coverage of all 6 parameters with examples and defaults. Output schema described. No gaps given the tool's complexity.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, but descriptions add extensive context beyond schema: e.g., why leave offsets at 0, how to get sync token, default values. Adds significant meaning.

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?

The description clearly states the tool's purpose: 'Read or update TimerMCP settings.' It distinguishes from sibling timing tools by focusing on configuration, not timer operations.

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?

Explicit guidance to 'Call with no args to read.' Explains when to use each parameter (e.g., leave offsets at 0). No explicit when-not-to-use, but context is clear.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/julanbasnet/timermcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server