Skip to main content
Glama
Sign In
Local MCP

Local MCP

by colibird-ai
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

create_reminder_list

Create a new list in Apple Reminders under the same account as the default list, so you can organize tasks into separate categories.

Instructions

Creates a new list in Apple Reminders (Reminders.app), in the same account as the default Reminders list (u...

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv3.0.352
  2. Removedv3.0.341
  3. Addedv3.0.330

TDQS

C2.7/5.0
Behavior2/5

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

With no annotations, the description carries the full behavioral burden. It does disclose one useful trait – the new list lands in the same account as the default Reminders list with no account selection – but says nothing about naming constraints, duplicate handling, failure modes, or what is returned, and cuts off mid-sentence.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single sentence that is cut off before completion, so it is not appropriately sized – it is under-specified rather than concise. Nothing is front-loaded beyond the verb-resource pairing.

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

Completeness2/5

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

For a mutation tool with no annotations, no output schema, and no parameters, the description should explain expected results or naming behavior. Instead it ends mid-word, leaving the agent without a complete picture of the operation's effect.

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?

The tool takes zero parameters and schema coverage is 100%, so the baseline is 4. However, the truncated text ("...list (u...") hints at a qualifier or condition the agent never receives, which is mildly confusing rather than clarifying, pulling this down to 3.

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?

The description names a specific verb and resource ("Creates a new list in Apple Reminders") and gives the list's scope, which distinguishes it from siblings like create_reminder and rename_reminder_folder. However, the sentence is truncated mid-clause ("...default Reminders list (u..."), so the purpose is stated but not fully finished.

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

Usage Guidelines2/5

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

There is no guidance on when to create a list versus using create_reminder, rename_reminder_folder, or get_reminder_folders, and no prerequisites or exclusions are stated. The truncated trailing clause may have contained such guidance, but as delivered none is present.

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