Skip to main content
Glama

Discard the timer

discard_timer
Destructive

Deletes the timer and its time, with no time entry. It cannot be undone: confirm with the user first.

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": "discard_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

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=false, so the safety profile is known. The description still adds real value by disclosing the side-effect model — the tracked time is discarded and no time entry is created — plus the irreversibility and the required confirmation step.

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?

Two short sentences, each carrying distinct information: the side effect first, then the irreversibility warning and the confirmation requirement. Nothing is redundant and the destructive warning is front-loaded.

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 one-parameter destructive mutation with a declared output schema, the definition covers the essential points: what is destroyed, what is not created, and that the user must confirm. It lacks only explicit routing to stop_timer as the non-destructive alternative.

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?

There is a single optional parameter with 100% schema description coverage, including the default ('the timer of now by default'). The description adds no additional meaning beyond the schema, so the baseline of 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?

The description uses a specific verb and resource ('Deletes the timer') and adds scope detail ('and its time, with no time entry'), which implicitly separates it from stop_timer. It stops short of naming a sibling, so sibling differentiation is inferred rather than stated.

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?

'confirm with the user first' gives a concrete operating instruction, and 'with no time entry' hints at when this is preferred over stopping a timer. However, no alternative tool is named and no explicit when-not-to-use condition is given beyond the confirmation prompt.

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