Skip to main content
Glama

Cancel timer

cancel_timer
DestructiveIdempotent

Cancel (discard) your running timer without creating a time entry. The elapsed time is lost. 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": "cancel_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.8/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and idempotentHint=true, but the description adds the concrete consequence: no time entry is created and the elapsed time is permanently lost. That is meaningful operational context beyond the flag. It does not mention whether a timer must currently be running or what happens if none exists.

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, front-loaded with the destructive consequence and ending with the invocation note. Every sentence carries distinct information and nothing is padded.

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 zero-required-parameter, non-open-world tool with rich annotations and no output schema, the description covers intent, consequence, and invocation cost. Minor gap: no statement of what happens when no timer is running, which matters for a destructive no-op.

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 the single optional idempotency_key is fully documented in the schema, so the baseline is 3. "No arguments needed" confirms all parameters are optional, but it slightly undersells the idempotency key, which the description never mentions as a retry-safety option.

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?

"Cancel (discard) your running timer" is a specific verb+resource, and "without creating a time entry" implicitly separates it from a stop/save flow. It stops short of naming the sibling (stop_timer) that an agent would pick when it wants to keep the time, so it is clear but not fully differentiated.

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?

"The elapsed time is lost" gives the agent enough to infer the when-to-use condition (discard vs. preserve time), but the guidance is implied rather than stated and no alternative tool is named or excluded. An agent must still infer that stop_timer is the counterpart.

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