Skip to main content
Glama
Sign In
icloud-mcp

icloud-mcp

by adamzaidi
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

create_reminder_list

Create a new iCloud Reminders list by name. Use it to separate reminders into lists; it fails if a list with that name already exists.

Instructions

Create a new Reminders list in iCloud Reminders. Fails if a list with that name already exists.

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

Input Schema

NameRequiredDescriptionDefault
nameYesName of the new list

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv2.8.0

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations, the description carries the full burden. It does disclose a real behavioral trait beyond the schema: the call fails if a list with that name already exists, making the operation non-idempotent on duplicates. However, it says nothing about permissions/account requirements, case sensitivity of the name match, or what is returned on success.

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 tight sentences with no filler, purpose front-loaded and the error precondition immediately after. Nothing is 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 one-parameter create tool with no output schema and no annotations, the description covers what it does and the main failure mode. A brief note on the return value or name-matching rules would make it fully complete.

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 single parameter has its own description ('Name of the new list'), so the schema already does the work. The description adds only that the name must be unique, a constraint rather than a semantic expansion of the parameter itself.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Create a new Reminders list') and scopes it to 'iCloud Reminders', which separates it from create_calendar and create_reminder in the sibling list. It does not explicitly name the related rename_reminder_list/delete_reminder_list tools, so it falls short of full sibling differentiation.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The duplicate-name failure condition implies when the call will be rejected, but there is no explicit guidance on when to use this versus rename_reminder_list or list_reminder_lists (e.g., check first to avoid collisions). Usage 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.

Deploy Server

Other Tools