timermcp

Overview Schema Source Related Servers Discussions Admin

History & Personal Bests

timer_history

Read-onlyIdempotent

Access personal bests, recent sessions, and lifetime totals for timers. Filter by name and limit results to review progress.

Instructions

Personal bests, recent finished runs, and lifetime totals. Read-only.

Args:

name (string, optional): Filter to one timer name; omit for everything.
limit (number, default 10): Max recent sessions returned (1–50).

Returns: { bests: [{name, best_ms?, count, total_ms}], recent: [{id, name, elapsed_ms, formatted, pb, splits, stopped_wall, target_ms?, over_under_ms?}], lifetime_ms, lifetime_sessions }

Great for "what's my record?", "how much have I tracked today?", or building a leaderboard recap for the user.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "timer_history"
  }
}

Input Schema

Name	Required	Description	Default
`name`	No	Filter to one timer name
`limit`	No	Max recent sessions

Output Schema

Name	Required	Description	Default
`bests`	Yes
`recent`	Yes
`lifetime_ms`	Yes
`lifetime_sessions`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.2.0Jul 14, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Annotations already cover idempotent and read-only. Description adds return structure and states read-only explicitly. 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.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Single sentence then structured args and return type. No fluff. Usage examples at end. Perfectly sized.

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 full annotations, output schema, and clear parameter docs, description closes all gaps. Complete for a history query tool.

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 parameters fully (100%). Description adds usage context: omit name for everything, limit range. Baseline 3, adds value.

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?

Clearly states it returns personal bests, recent runs, and lifetime totals. Directly distinguishes from timer_start/timer_stop by focusing on history.

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 concrete use cases (record, daily totals, leaderboard) and explains parameter usage. Lacks explicit when-not-to-use guidance.

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

Deploy Server