Skip to main content
Glama

Start timer (replaces a running one)

start_timer
Destructive

Start (or replace) your running timer on a subtask. There is at most one running timer per user; starting a new one replaces any existing. Stop it later with stop_timer to create a Draft time entry, or cancel it with cancel_timer to discard it. Supply subtask_id.

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": {
      "subtask_id": "<subtask_id>"
    },
    "name": "start_timer"
  }
}

Input Schema

NameRequiredDescriptionDefault
subtask_idYesId of the subtask to track time against.
descriptionNoOptional description of the work being tracked.
idempotency_keyNoOptional caller-supplied key; retrying with the same key returns the original result instead of acting twice.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior5/5

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

The annotations only flag destructiveHint=true and idempotentHint=false; the description explains exactly why — only one running timer per user exists and starting a new one replaces it — and discloses the downstream side effects (Draft time entry on stop, discard on cancel). That is genuine behavioral context beyond the structured fields.

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, front-loaded with the action and its replacement semantics before the lifecycle options. Slight redundancy between 'Start' and the parenthetical '(or replace)' that the second sentence repeats.

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?

For a three-parameter mutation with no output schema, the definition covers the key risks: overwriting a running timer and the two ways it can end. The only gap is that it never says what is returned on success, which an agent would have to discover by calling it.

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 coverage is 100% and each parameter already has its own description, so the schema does the heavy lifting. The description only restates requiredness ('Supply subtask_id') and adds nothing about the optional description or the idempotency_key parameter, which is baseline 3.

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?

States a specific verb and resource ('Start (or replace) your running timer on a subtask') and immediately qualifies the scope with the single-running-timer rule, so it is distinguishable from stop_timer and cancel_timer without opening any schema.

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?

Explicitly names the two sibling follow-up tools and what each does ('stop it later with stop_timer to create a Draft time entry, or cancel it with cancel_timer to discard it'), which is clear post-start guidance. It does not state when NOT to start a timer (e.g. logging past time), so it falls just short of full alternative routing.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources