Skip to main content
Glama

Delete a repeating wake-up

schedule_delete
DestructiveIdempotent

Delete one repeating wake-up rule for good, with its runs and history. Waiting runs never fire and it cannot be restored. It frees a rule slot and works after the plan ended too. Returns deleted: true; an unknown or already deleted schedule_id answers schedule_not_found. To pause or change it and keep its history, use schedule_update. wakeup_cancel is for one-shot calls only.

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": {
      "instance_id": "wkp_exampleexampleexample2",
      "schedule_id": "wsc_exampleexampleexample2"
    },
    "name": "schedule_delete"
  }
}

Input Schema

NameRequiredDescriptionDefault
instance_idYesUtility instance id from buy or list_utilities.
schedule_idYesschedule id (wsc_...) from schedule_create or schedule_list.
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. Changed2 schema fields changed
    • addedInput schema / examples
      Added value: +[
      +  {
      +    "instance_id": "wkp_exampleexampleexample2",
      +    "schedule_id": "wsc_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."
  2. 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}$"
  3. Added

TDQS

A4.6/5.0
Behavior5/5

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

The annotations already flag destructiveHint=true and idempotentHint=true, but the description adds what is actually destroyed (the rule, its runs and history), that waiting runs never fire, and that it cannot be restored. It also discloses the success return (deleted: true) and the schedule_not_found error case, consistent with idempotentHint since re-deleting yields a not-found answer rather than a second mutation.

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?

Four short sentences, front-loaded with the irreversible effect, then the outcome, then routing to alternatives. No filler and nothing buried.

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 destructive three-parameter tool with no output schema, this covers consequences, return behavior, error semantics and sibling routing. It stops short of mentioning authorization or the passport_token fallback path, which is the only remaining gap.

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 instance_id and schedule_id already documented in the schema, so the baseline is 3. The description adds only marginal parameter meaning by explaining that an unknown or already-deleted schedule_id returns schedule_not_found, and it says nothing about the optional passport_token.

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 opens with a specific verb and resource, 'Delete one repeating wake-up rule', and immediately bounds the scope to a single rule. It distinguishes itself from schedule_update (pause/change) and wakeup_cancel (one-shot calls), so an agent can select it without opening any 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?

It gives explicit alternatives and the conditions that select them: use schedule_update to pause or change while keeping history, and wakeup_cancel only for one-shot calls. It also notes the tool still works after the plan ended, which prevents an agent from skipping it under a wrong assumption.

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.