Skip to main content
Glama
Sign In
clockify-mcp

clockify-mcp

by duynhannguyen
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Stop the running Clockify timer

stop_timer
Idempotent

Stop the active Clockify timer and retrieve the logged duration. If no timer is running, this reports that plainly.

Instructions

Stop the currently running Clockify timer and report the logged duration. Reports plainly when no timer was running.

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
endNoWhen the timer should stop. Defaults to now.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4.2/5.0
Behavior4/5

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

Annotations indicate this is a mutating but non-destructive, idempotent operation. The description adds useful behavioral detail by stating it reports the logged duration and gives a plain response when no timer was running, which aligns with the idempotent annotation.

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?

The description is two short sentences with no filler. The primary action is stated first, followed by the return behavior, making it easy to scan.

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 simple tool with one optional parameter and no output schema, the description covers the core behavior, the no-timer case, and what the caller can expect in the response. It is sufficient for an agent to select and invoke the tool correctly.

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% for the single optional parameter 'end.' The description does not add any additional meaning beyond the schema, so the baseline of 3 is appropriate.

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?

The description uses a specific verb and resource: 'Stop the currently running Clockify timer.' It clearly differentiates from siblings like start_timer and current_timer, and adds the reporting behavior so the agent knows what the tool returns.

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?

The description makes it clear the tool applies to a currently running timer and that it handles the no-timer case gracefully. It does not explicitly name alternatives, but the context signals and sibling names make the usage context obvious.

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

Deploy Server

Other Tools