Skip to main content
Glama

Pause the timer

pause_timer

Pauses the running timer. timer_id names the timer that you saw; 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": "pause_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.2/5.0
Behavior2/5

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

Annotations already declare this is a non-read-only, non-destructive, non-idempotent mutation, so the safety profile is covered. The description adds nothing beyond that: it does not say what happens if no timer is running, whether pausing is reversible via resume_timer, or what a repeated pause call does — a meaningful gap given idempotentHint=false.

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 sentences, front-loaded with the action and with no filler. The word "optional" is mildly redundant against the schema's zero required parameters, but nothing else is wasted.

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?

The tool is simple (one optional UUID parameter, output schema present), so the bar is low and the safety profile comes from annotations. Still, the definition never addresses failure behavior (no running timer) or the pause/resume lifecycle, which is the main thing an agent would want to know.

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 description coverage is 100%, and the schema already explains that timer_id is 'the timer that the client saw; the timer of now by default.' The description's "names the timer that you saw; optional" restates this rather than adding format, lookup, or defaulting semantics.

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?

Specific verb plus resource: "Pauses the running timer" tells an agent exactly what happens and to what. It does not explicitly distinguish itself from close siblings such as stop_timer or resume_timer, so an agent must still infer the boundary rather than being told.

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 by the word "Pauses" — the natural reading is 'use when you want to pause a running timer.' There is no statement of when not to use it versus stop_timer/resume_timer, nor any mention of preconditions (e.g., that a timer must 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