Local MCP

Get Reminder Folders

get_reminder_folders

Read-only

Lists the lists (folders) in Apple Reminders (Reminders.app) on this Mac. Every answer carries as_of (when the list snapshot was read) and cache_age_seconds; if cache_age_seconds is above 0 the snapshot is that many seconds old and a list created since then may be missing — call again to force a re-read. For Microsoft To Do use todo_get_folders instead. Each entry's permissions carries only the permissions this service has (read, send, write; a key that is missing does not apply). true: allowed in the account's boxes (LMCP's icon → My apps → open the app's row → the account's Read · Send · Write) and the item accepts it. false: turned off there, or the item is read-only (read_only: true).

Input Schema

Name	Required	Description	Default
No arguments

Output Schema

Name	Required	Description
`note`	No	Present only when the snapshot is not fresh: says how old it is and what may be missing.
`as_of`	No	ISO 8601 UTC instant when this list snapshot was read from EventKit (not when iCloud last synced).
`count`	No
`lists`	No
`cache_age_seconds`	No	Age of the snapshot. 0 means it was read fresh for this call.

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedOct 22, 2026

addedOutput schema / properties / lists / items / properties / permissions

Added value: +{
+  "properties": {
+    "read": {
+      "type": "boolean"
+    },
+    "send": {
+      "type": "boolean"
+    },
+    "write": {
+      "type": "boolean"
+    }
+  },
+  "type": "object"
+}

addedOutput schema / properties / lists / items / properties / read_only

Added value: +{
+  "description": "true: the system reports this item as not modifiable. Absent when it cannot tell.",
+  "type": "boolean"
+}

Changed3 schema fields changedAug 26, 2026

addedOutput schema / properties / as_of

Added value: +{
+  "description": "ISO 8601 UTC instant when this list snapshot was read from EventKit (not when iCloud last synced).",
+  "type": "string"
+}

addedOutput schema / properties / cache_age_seconds

Added value: +{
+  "description": "Age of the snapshot. 0 means it was read fresh for this call.",
+  "type": "integer"
+}

addedOutput schema / properties / note

Added value: +{
+  "description": "Present only when the snapshot is not fresh: says how old it is and what may be missing.",
+  "type": "string"
+}

AddedAug 2, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already declare readOnlyHint/destructiveHint=false, so the safety profile is covered. The description adds valuable context beyond annotations: the as_of/cache_age_seconds staleness semantics and the meaning of the permissions map, which an agent would otherwise have to infer.

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?

The primary purpose and the cache caveat are front-loaded in the first two sentences. The permissions paragraph is dense and slightly hard to parse, but it earns its place by explaining a non-obvious return field.

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-value explanation isn't strictly required, yet the description still clarifies as_of, cache_age_seconds, and the permissions map. Combined with a clear cross-tool pointer, this is complete enough to call correctly, with only minor verbosity as a downside.

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?

The tool takes zero parameters, so the baseline is 4. There is no parameter to document, and the description correctly does not waste effort on nonexistent inputs.

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 ('Lists the lists (folders) in Apple Reminders on this Mac'), and explicitly distinguishes itself from todo_get_folders. An agent can identify this as the Apple Reminders folder-enumeration tool without inspecting 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?

Explicitly routes the agent to todo_get_folders for Microsoft To Do and explains the cache re-read condition ('call again to force a re-read'). Clear context, though it doesn't enumerate other when-not scenarios.

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

All Local MCP tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.