Skip to main content
Glama

Stop the timer

stop_timer

Stops the timer and records its time as a time entry, in time_entry. timer_id is optional.

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": "stop_timer"
  }
}

Input Schema

NameRequiredDescriptionDefault
timer_idNoThe timer that the client saw; the timer of now by default

Output Schema

NameRequiredDescriptionDefault
timerYesThe timer of the member of the token, or `null`
time_entryNo`billable`, `currency`, `hourly_rate`, `amount`, `invoice_id` and `invoice_number` are only for a role that sees amounts, and `cost_rate`, `cost_currency` and `cost` only for a role that sees costs.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare this is not read-only, not destructive, and not idempotent; the description usefully adds what the mutation actually does (creates a time entry). However, it is silent on the consequences the annotations imply matter here — e.g. what happens if called twice or when no timer is running, and whether the resulting entry can be undone.

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?

Two short clauses, front-loaded with the action and its effect. The phrase 'in `time_entry`' is slightly awkward but not wasteful; nothing is padded.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists, so return values need not be explained. Still, for a non-idempotent mutation, the description omits the edge-case behavior (already-stopped or missing timer) that an agent needs to call it safely, leaving a meaningful gap.

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 already documents `timer_id` as a UUID with a 'timer of now by default' fallback. The description restates that the parameter is optional but adds no new meaning, so the baseline 3 applies.

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+resource (stop the timer) and adds the key side effect that the timer's elapsed time is converted into a time entry in `time_entry`. That side effect distinguishes it in principle from discard_timer, but the description never names or contrasts with that sibling, so differentiation is left implicit.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is only implied: an agent can infer 'call this to end a running timer and keep the time'. There is no explicit statement of when to prefer this over discard_timer, nor any precondition such as a timer needing to be running.

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