Skip to main content
Glama

delete_reminder_list

DestructiveIdempotent

Delete an empty Reminders list only after setting confirm to true; deletion is refused for non-empty, read-only, or default lists.

Instructions

Delete an empty reminder list. It is refused when the list has any reminder (completed or not), when the list is read-only, and for the default list. It needs 'confirm' true, also for an empty list. Without it, nothing is deleted. The result has a copy of the list (name and account), so create_reminder_list can make it again.

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": {
      "list": "<list>"
    },
    "name": "delete_reminder_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
listYesList name or id. Names ignore case.
confirmNoMust be true to delete the list. Without it, nothing is deleted.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.4/5.0
Behavior5/5

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

Annotations already flag destructive and non-read-only, so the description earns credit by adding what they cannot: the exact refusal conditions, the mandatory confirm flag, the no-op behavior without it, and the fact that the response returns a copy of the list (name and account) so it can be recreated. That is rich behavioral context beyond structured fields.

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 sentences, front-loaded with the action and its constraints, with the recovery hint last. The only waste is the duplication of 'Without it, nothing is deleted', which already appears verbatim in the confirm parameter description.

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?

For a two-parameter destructive tool with no output schema, the description covers everything an agent needs: eligibility rules, the confirm gate, failure modes, and the shape of the returned result. Nothing material is left to inference.

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% and the schema already documents both 'list' (name or id, case-insensitive) and 'confirm' (must be true). The description restates the confirm requirement rather than adding new semantics such as id-format expectations, so the schema remains the primary source.

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 ('Delete an empty reminder list') and immediately narrows scope with the 'empty' qualifier, which distinguishes it from the sibling delete_reminder and from a bulk list deletion. An agent can tell what this does without opening the schema.

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?

Gives explicit preconditions and refusal cases (list contains reminders, read-only list, default list) and a required-confirm gate, which effectively tells the agent it must clear reminders first. It stops short of naming delete_reminder as the tool to do that clearing, so the routing to the alternative is implied rather than stated.

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