Skip to main content
Glama
Sign In
@chitmark/haven-mcp

@chitmark/haven-mcp

by nonameuserd
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

wake_cancel

Cancel an active wake watch by its ID, causing subsequent wake_wait calls to return idle immediately.

Instructions

Cancel a Wake watch by id. TTL and event caps end it anyway; this ends it now. A cancelled watch stops matching, so wake_wait on it returns idle.

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": {
      "wakeId": "<wakeId>"
    },
    "name": "wake_cancel"
  }
}

Input Schema

NameRequiredDescriptionDefault
wakeIdYesWatch id returned by the wake tool.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / wakeId / description
      Added value: +"Watch id returned by the wake tool."
  2. First observedv0.1.0

TDQS

A4.2/5.0
Behavior4/5

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

Annotations indicate readOnlyHint=false, so mutation is expected. The description adds useful context: that the watch stops matching and that wake_wait on it returns idle. It also notes that TTL and event caps would end it anyway, framing this as an early termination. This exceeds what annotations alone provide, with no contradictions.

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 concise sentences with no redundancy. The primary action is front-loaded, and each sentence adds essential context (termination mechanism, effect on wake_wait). No wasted words.

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 single-parameter tool with a clear purpose and effect on a sibling, the description is complete. It doesn't have an output schema, but it explains the outcome via wake_wait behavior. Missing edge-case handling (e.g., invalid id) is not required for basic usage.

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%, and the schema already describes wakeId as 'Watch id returned by the wake tool.' The description does not add further parameter semantics 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 clearly states the action ('Cancel a Wake watch by id') and the resource (Wake watch). It distinguishes from siblings by noting TTL/event caps as alternative termination mechanisms and explicitly mentions the effect on wake_wait (returns idle). This makes the tool's purpose unambiguous.

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 it: when you want to end a watch immediately rather than waiting for natural expiration. It also clarifies the behavioral consequence for wake_wait. However, it doesn't explicitly state scenarios where cancellation is inappropriate or alternatives to prefer, but the context is sufficient for most use cases.

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