Skip to main content
Glama

Cancel a wake-up call

wakeup_cancel
DestructiveIdempotent

Cancel a wake-up call that has not fired yet (scheduled or retrying): it never fires and shows canceled. Another status answers wakeup_not_cancelable, an unknown wakeup_id answers wakeup_not_found: nothing changes. Works after the plan ended. Repeating ones: schedule_update or schedule_delete.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "wakeup_id": "wak_exampleexampleexample2",
      "instance_id": "wkp_exampleexampleexample2"
    },
    "name": "wakeup_cancel"
  }
}

Input Schema

NameRequiredDescriptionDefault
wakeup_idYesThe call's id (wak_...) from wakeup_schedule or wakeup_list.
instance_idYesUtility instance id from buy or list_utilities.
passport_tokenNoYour amp_ token, only if you have no app sign-in and cannot send a header.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / wakeup_id / description
      Previous value: -"wakeup_id from wakeup_schedule or wakeup_list."New value: +"The call's id (wak_...) from wakeup_schedule or wakeup_list."
  2. Changed2 schema fields changed
    • addedInput schema / examples
      Added value: +[
      +  {
      +    "instance_id": "wkp_exampleexampleexample2",
      +    "wakeup_id": "wak_exampleexampleexample2"
      +  }
      +]
    • changedInput schema / properties / passport_token / description
      Previous value: -"Your amp_ token, only if your app has no sign-in and cannot send it as an Authorization header."New value: +"Your amp_ token, only if you have no app sign-in and cannot send a header."
  3. Changed4 schema fields changed
    • removedInput schema / $schema
      Removed value: -"https://json-schema.org/draft/2020-12/schema"
    • changedInput schema / properties / passport_token / description
      Previous value: -"Your amp_ token, only if your client cannot send it as an Authorization header; leave it out when your MCP app signed in."New value: +"Your amp_ token, only if your app has no sign-in and cannot send it as an Authorization header."
    • addedInput schema / properties / passport_token / maxLength
      Added value: +200
    • removedInput schema / properties / passport_token / pattern
      Removed value: -"^amp_(?:s_)?[A-Za-z0-9_-]{43}$"
  4. Changed3 schema fields changed
    • addedInput schema / additionalProperties
      Added value: +false
    • changedInput schema / properties / passport_token / description
      Previous value: -"Leave it out when your MCP app signed in to AgentMart (it is refused then). Otherwise your passport bearer token (amp_...) or session token (amp_s_...), only if your client cannot send it as an Authorization header. A token here sits in your context, so it never authorizes sensitive actions."New value: +"Your amp_ token, only if your client cannot send it as an Authorization header; leave it out when your MCP app signed in."
    • addedInput schema / properties / wakeup_id / description
      Added value: +"wakeup_id from wakeup_schedule or wakeup_list."
  5. First observed

TDQS

A4.5/5.0
Behavior5/5

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

Annotations only declare destructive/idempotent/non-readOnly; the description adds the actual state transition ("it never fires and shows canceled"), the two failure codes and their no-op guarantee, and the edge case that it still works after the plan ended. This is genuine behavior beyond the structured hints, with no contradiction of them.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Dense and front-loaded: eligibility, outcome, error semantics, then alternatives, in three short sentences. It loses a point for telegraphic fragments ("Repeating ones: schedule_update or schedule_delete") that are terse to the point of being syntactically incomplete.

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 3-parameter mutation with no output schema, the description covers eligibility, effects, failure modes, and alternatives, which is most of what an agent needs. It stops short of describing the success response shape or what happens on a second cancel of an already-canceled wake-up, a small gap given idempotentHint=true.

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%, so wakeup_id's origin (wak_... from wakeup_schedule or wakeup_list) and instance_id are already fully documented in the schema. The description only alludes to wakeup_id via the unknown-id error case and says nothing about passport_token, so it adds little beyond the schema's baseline.

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?

States a specific verb and resource ("Cancel a wake-up call") plus the eligibility scope ("has not fired yet (scheduled or retrying)"). It also distinguishes itself from schedule_update/schedule_delete for repeating wake-ups, so an agent can pick it out of the sibling set without opening a schema.

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

Usage Guidelines5/5

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

Explicitly names when it applies (scheduled or retrying, not yet fired), what happens when it does not apply (other statuses return wakeup_not_cancelable, unknown ids return wakeup_not_found, "nothing changes"), and routes repeating wake-ups to schedule_update or schedule_delete. That is a full when/when-not/alternative matrix.

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.