Skip to main content
Glama

Stop timer

stop_timer
DestructiveIdempotent

Stop your running timer (a paused one too). The time it ran - its pauses left out - is saved as a Draft time entry automatically. Returns the created time entry. No arguments needed.

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
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

A3.9/5.0
Behavior4/5

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

Annotations already flag this as destructive, non-read-only, and idempotent, so the safety profile is covered. The description adds genuinely useful behavior beyond that: the recorded duration excludes pauses, the result is auto-saved as a Draft time entry, and the created entry is returned. It does not discuss what happens to the timer afterwards or any permission requirements, keeping it short of a 5.

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?

Three short sentences with zero filler: the action and scope come first, the side effect second, the return value third. Every sentence carries distinct information.

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?

For a single-mutation tool with no output schema, the description covers the action, the timer-state edge case, the persist side effect, the return value, and the absence of required inputs. There is no output schema to justify omitting return details, and it supplies them anyway.

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% with a single optional idempotency_key fully documented in the schema, so the baseline is 3. The description's "No arguments needed" is accurate for required parameters but adds no meaning about the idempotency key beyond what the schema already explains.

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 and resource ("Stop your running timer") plus an important scope qualifier ("a paused one too") and the resulting side effect (a Draft time entry is created). It does not distinguish itself explicitly from the sibling cancel_timer, so an agent must infer that difference from the sibling's name alone.

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 context is implied by "your running timer" and the note that paused timers are also handled, which tells the agent this covers both states. There is no explicit when-not guidance and no reference to cancel_timer, which is the obvious alternative an agent might otherwise choose.

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