Skip to main content
Glama

Delete a schedule

delete_schedule
Destructive

Permanently removes a schedule and its firing history while keeping the underlying block. Call without confirm first to preview; set confirm=true to execute deletion.

Instructions

Permanently removes a schedule and its history. The block stays; only the firing goes. Requires confirm=true; call without confirm first to preview. To stop it temporarily, pause_schedule keeps the history.

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": {
      "triggerId": "<triggerId>"
    },
    "name": "delete_schedule"
  }
}

Input Schema

NameRequiredDescriptionDefault
confirmNoMust be true to delete. Omit/false returns a preview only.
triggerIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.53.0

TDQS

A4.5/5.0
Behavior5/5

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

Annotations only flag destructiveHint=true, but the description adds that removal is permanent, that history is destroyed while the block survives, and that a confirm=true gate exists with a preview path first. That is substantive behavioral context an agent cannot get from the annotation alone.

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?

Four short, front-loaded sentences with no filler; each carries a distinct fact (permanence, scope, confirm gate, alternative). Slightly dense telegraphic phrasing ('only the firing goes') but nothing wasted.

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 two-parameter tool with no output schema, the irreversible effect, preview requirement, and pause alternative are all covered. The main omission is any hint about what the preview returns or what triggerId refers to.

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?

The confirm parameter's preview behavior is already fully documented in the schema, so the description largely restates it, and the required triggerId is left with no explanation in either the schema or the description at 50% coverage. It does not compensate for the undocumented required parameter.

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 names a specific verb and resource ('Permanently removes a schedule') and scopes the effect ('and its history'), then immediately clarifies what is not affected ('The block stays; only the firing goes'), which distinguishes it from pause_schedule.

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 states the delete workflow explicitly ('Requires confirm=true; call without confirm first to preview') and names the alternative for the temporary case ('To stop it temporarily, pause_schedule keeps the history'), giving both when-to-use and when-not-to-use guidance.

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