Skip to main content
Glama

create_reminder_list

Create a new reminder list by name, optionally assigning it to a specific account such as iCloud. Fails if a list with the same name already exists.

Instructions

Create a reminder list. It fails when a list with the same name (any case) already exists. Without 'source' the list goes into the account of the default list.

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.
sourceNoAccount name or id, for example iCloud. Default: the account of the default list.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.9/5.0
Behavior4/5

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

The annotations already declare this is a non-read-only, non-destructive, closed-world operation. The description adds important behavior beyond annotations by disclosing the case-insensitive duplicate-name failure and the default account behavior when 'source' is omitted.

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?

The description is three short sentences, front-loaded with the purpose and followed by the key failure and default-account constraints. Every sentence adds useful information with no wasted wording.

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 simple two-parameter creation tool with full schema coverage and annotations, the description covers the main purpose, duplicate-name constraint, and default account behavior. It could be slightly more complete by clarifying whether duplicate checks apply within the target account, but no major gap prevents correct invocation.

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?

Schema coverage is complete, so the baseline is 3. The description still adds meaning for the 'name' parameter by clarifying that duplicate names are rejected regardless of case, and it reinforces the default behavior for 'source'.

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 states a specific verb and resource: create a reminder list. It is distinguishable from create_reminder by the 'list' resource, but it does not explicitly differentiate itself from any sibling tool.

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 useful operational context: duplicate names fail and omitting 'source' uses the default list's account. However, it does not explicitly say when to use this tool instead of alternatives such as create_reminder.

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