Skip to main content
Glama
Sign In

zerm

by dev.zerm
OverviewDiscussionsAdmin

Cancel Scheduled Callback

timer_cancel
DestructiveIdempotent

Cancel a pending timer using the id returned by timer_schedule. The id is the authorization: holding it is what proves you scheduled the timer, so keep it secret. Already-delivered or already-cancelled timers return cancelled=false.

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": {
      "id": "<id>"
    },
    "name": "timer_cancel"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesThe timer id returned by timer_schedule.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / id / description
      Added value: +"The timer id returned by timer_schedule."
  2. First observed

TDQS

A4.7/5.0
Behavior5/5

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

Beyond the annotations (destructive, idempotent), the description adds critical context: the id acts as authorization and must be kept secret, and that already-delivered or already-cancelled timers return cancelled=false, explaining the idempotency behavior in practical terms.

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 sentences, each with a distinct purpose: action, security caveat, and edge-case behavior. No wasted words, and the most important action is front-loaded.

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?

The tool is simple (one parameter, no output schema) and annotations cover safety. The description provides all necessary operational details: cancellation action, id source, secret handling, and behavior for non-pending timers, making it fully self-sufficient.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The schema already covers the id parameter fully (100% coverage), so baseline is 3. The description adds extra meaning by framing the id as a secret authorization token returned by timer_schedule, which is valuable semantic information beyond the schema.

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 clearly states 'Cancel a pending timer using the id returned by timer_schedule' with a specific verb and resource, distinguishing it from siblings like timer_schedule and timer_status by focusing on the cancellation action.

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 implies when to use this tool (to cancel a pending timer) and references the id from timer_schedule. It does not explicitly name alternatives, but the context is clear enough; the edge-case note about already-delivered/cancelled timers provides additional operational context.

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

All zerm toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources