Skip to main content
Glama
Sign In
icloud-mcp

icloud-mcp

by adamzaidi
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

delete_reminder_list

Delete an empty Reminders list by exact name, with an optional dry-run to preview changes without modifying data.

Instructions

Delete a Reminders list. The list must be empty first, and the name must match exactly one list.

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

Input Schema

NameRequiredDescriptionDefault
nameYesExact name of the list to delete
dryRunNoIf true, report exactly what would change and do not modify anything

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv2.8.0

TDQS

A4.1/5.0
Behavior3/5

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

With no annotations, the description has to carry the whole behavioral burden. It usefully discloses a non-obvious precondition: the list must be empty. It does not say what happens when that precondition fails (error or refusal), whether the deletion is permanent, or whether confirmation is required.

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?

Two sentences, no filler, and the destructive action is named before its preconditions. Every clause carries information the agent needs.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

This is an unannotated mutation with no output schema, so the description should do more. The precondition and the name-uniqueness rule are covered, but failure behavior, irreversibility, and how dryRun changes the outcome are left to the schema and to inference.

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%, so both parameters are already documented and the baseline is 3. The description adds real meaning beyond the schema by saying the name must resolve to exactly one list, which tells the agent that an ambiguous name will not delete anything. It says nothing about dryRun, but the schema covers that field.

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?

"Delete a Reminders list" gives a specific verb plus resource, and the noun "list" cleanly separates it from the sibling delete_reminder and from delete_calendar or delete_mailbox. An agent can pick it out of the sibling set 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?

It states the prerequisite (the list must be empty) and the name-matching condition (the name must match exactly one list), which controls when a call will succeed. It does not point at alternatives such as delete_reminder for removing individual reminders or rename_reminder_list, so it stops just short of full routing guidance.

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

Deploy Server

Other Tools