Skip to main content
Glama
Sign In
icloud-mcp

icloud-mcp

by adamzaidi
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

list_reminders

Fetch reminders from iCloud Reminders by list or across all lists, with optional completed items and a result limit.

Instructions

List reminders from iCloud Reminders. Omit listName to fetch from all lists.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_reminders"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMax reminders to return (default 50)
listNameNoList name from list_reminder_lists (omit for all lists)
includeCompletedNoInclude completed reminders (default false)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv2.8.0

TDQS

B3.3/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden. 'List' implies a read-only operation, but the description says nothing about return volume, the default limit of 50, whether completed items are excluded by default, ordering, or pagination — all left implicitly to the schema or undocumented.

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 short sentences with zero waste; the core purpose is front-loaded and the scope rule follows immediately.

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?

For a simple zero-required-parameter read tool with full schema coverage, the description is minimally adequate. But with no annotations and no output schema, it should disclose return behavior (default cap, whether completed reminders appear) rather than leaving that to the schema defaults alone.

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 description coverage is 100%, with defaults and the list_reminder_lists cross-reference already documented inline. The description's note about omitting listName merely restates the schema, adding no new meaning to the three parameters.

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 ('List reminders from iCloud Reminders') and clarifies the scope of the listing. It doesn't explicitly distinguish itself from siblings like get_reminder or list_reminder_lists, but the list-vs-single retrieval distinction is clear from the verb.

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 description gives one concrete usage rule ('Omit listName to fetch from all lists') and the schema cross-references list_reminder_lists for valid names. However, it never states when to use this tool versus get_reminder or list_reminder_lists, so the routing guidance is only implied.

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