Skip to main content
Glama
Sign In
HomarUScc

HomarUScc

by kcdjmaxx
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

timer_cancel

Provide a timer ID or name to cancel a scheduled timer, preventing it from firing.

Instructions

Cancel a scheduled timer

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "name": "<name>"
    },
    "name": "timer_cancel"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesTimer ID or name to cancel

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.5.0

TDQS

B3.2/5.0
Behavior2/5

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

No annotations are provided, so the description must carry full behavioral burden. It only states the action without disclosing side effects, idempotency, error behavior, or whether the timer is immediately removed or simply marked as cancelled.

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?

Single sentence, front-loaded, and zero wasted words. It is appropriately sized for a simple tool with one parameter and no additional context needed.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Despite low complexity, the tool performs a mutation with no annotations, no output schema, and no explanation of consequences or usage context. The description alone is insufficient for an agent to fully understand when and how to use it safely.

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 'name' described as 'Timer ID or name to cancel'. The description adds no additional parameter meaning beyond the schema, so baseline 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 'Cancel a scheduled timer' uses a specific verb and resource, clearly distinguishing from the sibling tool 'timer_schedule'. It precisely communicates the tool's function without ambiguity.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides no guidance on when to use this tool versus alternatives, no prerequisites, and no exclusions. It does not mention that it is the counterpart to timer_schedule or any specific context for cancellation.

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