Skip to main content
Glama
Sign In
heznpc

AirMCP

by heznpc
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

List Reminders

list_reminders
Read-onlyIdempotent

Retrieve reminders from Apple Reminders, optionally filtering by list name or completed status and paginating results with limit and offset.

Instructions

List reminders. Optionally filter by list name and/or completion status. Supports pagination via limit/offset.

Input Schema

NameRequiredDescriptionDefault
listNoFilter by list name
limitNoMax number of reminders to return (default: 200)
offsetNoNumber of reminders to skip for pagination (default: 0)
completedNoFilter by completed status (true/false). Omit to list all.

Output Schema

NameRequiredDescriptionDefault
totalYes
offsetYes
returnedYes
remindersYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv2.16.7
    • addedOutput schema / properties / reminders / items / properties / flagged / description
      Added value: +"Actual flag status; omitted (unknown) when EventKit is used"
    • changedOutput schema / properties / reminders / items / required
      Previous value: -[
-  "id",
-  "name",
-  "completed",
-  "dueDate",
-  "priority",
-  "flagged",
-  "list"
-]New value: +[
+  "id",
+  "name",
+  "completed",
+  "dueDate",
+  "priority",
+  "list"
+]
  2. Changed2 schema fields changedv2.16.6
    • removedOutput schema / properties / reminders / items / properties / dueDate / anyOf
      Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
    • addedOutput schema / properties / reminders / items / properties / dueDate / type
      Added value: +[
+  "string",
+  "null"
+]
  3. Changed2 schema fields changedv2.16.5
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
    • changedOutput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
  4. Changed4 schema fields changedv2.14.0
    • removedInput schema / additionalProperties
      Removed value: -false
    • addedInput schema / properties / offset / maximum
      Added value: +9007199254740991
    • addedOutput schema / properties / reminders / items / properties / dueDate / anyOf
      Added value: +[
+  {
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]
    • removedOutput schema / properties / reminders / items / properties / dueDate / type
      Removed value: -[
-  "string",
-  "null"
-]
  5. Addedv2.12.0
  6. Removedv2.3.1
  7. First observedv0.3.0

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world, so the safety profile is fully covered elsewhere. The description adds only that results can be filtered and paged, and says nothing about ordering, totals, or truncation behavior.

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?

Three short sentences, front-loaded with the core action followed by filtering and paging capability. Every sentence carries a distinct piece of information with no filler.

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?

An output schema exists so return values need not be described, and annotations cover the safety profile. The description plus schema covers all four optional parameters; only ordering and result-size expectations are unstated.

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 per-parameter descriptions and defaults, so the schema does the semantic work. The description restates the same filters and pagination mechanism without adding format, default, or interaction details.

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") and the two filterable dimensions, which is enough to tell it apart from list_notes and list_events. It stops short of naming any sibling or distinguishing boundary explicitly.

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?

Usage is implied by the optional filters and pagination note, but there is no statement of when to prefer this over a search tool or what to do when the result set is large beyond paging. No exclusions or alternatives are given.

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