Skip to main content
Glama

Delete a routine

delete_routine
DestructiveIdempotent

Permanently delete ONE of the user's own routines by id (from get_routines), with its history. The built-in morning and evening routines cannot be deleted (ok:false managed_routine): switch them off with update_routine enabled:false, which is also the better choice when the user may want a routine back. To skip a routine for one day use delete_task with its id and that date. Returns {ok:true, id, deleted:true, title}; ok:false (not_found, not_a_routine, managed_routine) deleted nothing. Preview rule: if this is the second task or routine change within about 90 seconds, nothing is saved and the result is needs_preview with the pending and saved changes - show them to the user and call again with confirm:true only after they agree.

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": "delete_routine"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesThe routine id from get_routines.
confirmNoSet true ONLY after the user has seen and approved this change in a preview you showed them (needed when a request changes more than one task or routine). Never set it on your own. Default false.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already declare destructive=true, idempotent=true, readOnly=false, so the safety profile is covered; the description adds genuinely new behavior: history is destroyed with the routine, managed routines are rejected with a managed_routine error, error codes (not_found, not_a_routine, managed_routine) confirm nothing was deleted, and a preview gate can intercept the call. The only thing left implicit is that the idempotent hint applies to already-deleted ids, but the not_found code covers it.

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?

Front-loaded with the core action and destructive scope, then alternatives, then return contract, then the preview rule. Dense but every sentence carries operational information; the preview paragraph is long and slightly compressed with parenthetical error codes, but nothing is wasted.

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?

No output schema exists, yet the description supplies the success payload ({ok:true, id, deleted:true, title}), the failure codes with their guarantee that nothing was deleted, and the full needs_preview flow including how to re-call with confirm. Nothing an agent needs to invoke this destructive tool correctly is missing.

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?

Schema coverage is 100% and both parameters are described there, so the baseline is 3. The description goes beyond the schema by explaining when confirm becomes necessary at all — the second task/routine change within ~90 seconds triggers needs_preview — which makes the confirm parameter's purpose concrete rather than a generic warning.

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 ("Permanently delete ONE of the user's own routines by id") and immediately scopes it: own routines only, id sourced from get_routines, history included. An agent can distinguish this from delete_task, update_routine, and get_routines without opening any other definition.

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?

Gives explicit when-not and alternatives: built-ins cannot be deleted, so use update_routine enabled:false (also the better choice when the routine may be wanted back), and delete_task with a date for a one-day skip. That is exactly the routing information an agent needs to avoid a failed or wrong call.

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.

Resources