Skip to main content
Glama
julanbasnet

timermcp

by julanbasnet

Stop Timer

timer_stop

Stop a running timer and get the official elapsed time in milliseconds. Use trim_to_ms to cap the time if you forgot to stop it.

Instructions

Stop a running timer and get the official elapsed time in milliseconds.

elapsed_ms = (monotonic stop-stamp − monotonic start-stamp) − start_offset_ms − stop_offset_ms. raw_elapsed_ms is the pure unadjusted monotonic difference. Because both stamps are taken server-side, symmetric pipeline latency cancels; offsets exist only to bias out asymmetry if the user wants.

Args:

  • name (string, default "main"): Which timer to stop.

  • stop_offset_ms (number, optional): Override the configured stop-side latency handicap for this stop only.

  • trim_to_ms (number, optional): Cap the recorded time. Use when the user forgot to stop a runaway timer and tells you how long they actually worked (e.g. "I only worked 25 minutes" → trim_to_ms 1500000). The session records the capped time and is flagged trimmed.

Returns: { session: {name, elapsed_ms, raw_elapsed_ms, formatted, splits, pb, pb_margin_ms?, target_ms?, over_under_ms?, id}, announcement, card_path, card_url }

A shareable SVG result card is written on every stop (card_path on disk, card_url served by the dashboard).

IMPORTANT: Relay the 'announcement' to the user — big finish energy if it's a PB. Quote the exact millisecond figure.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameNoTimer to stopmain
trim_to_msNoCap the recorded time at this many ms (runaway-timer rescue)
stop_offset_msNoLatency handicap subtracted from the final time (stop side)

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
sessionYes
card_urlYes
card_pathYes
announcementYes
Behavior4/5

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

Annotations indicate mutation, and the description transparently explains the elapsed time calculation, that a card is written to disk, and the return structure. No contradictions.

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 and emphasis on important notes. Slightly verbose but front-loads the core action. Every sentence is informative.

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?

Covers purpose, usage, parameters, side effects, and return values. With output schema present, the description is complete enough for an agent to use correctly.

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

Parameters4/5

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

Schema covers all parameters, but the description adds value by explaining trim_to_ms as a runaway timer rescue and stop_offset_ms as a latency handicap, which is 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?

The description clearly states it stops a running timer and returns elapsed time. It distinguishes from sibling tools like timer_cancel (which cancels without recording) and timer_start.

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?

Provides clear context on when to use the tool and includes important notes like relaying the announcement and using trim_to_ms for runaway timers. Does not explicitly state when not to use, but the context is sufficient.

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