Skip to main content
Glama
epinethrone

icloud-mcp

by epinethrone
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

contacts_list_birthdays

Read-only

List iCloud contacts whose birthdays fall within the next N days, sorted soonest first, with dates, days until, and age they turn for planning greetings or reminders.

Instructions

List the owner's contacts whose birthday falls within the next N days, soonest first, with the date, days until it and the age they turn.

Use when: the owner asks whose birthday is coming up, or you are planning greetings or reminders. Not for one person's birthday (use contacts_get_contact) or for finding someone by name (use contacts_search_contacts). Parameters:

  • days: a whole number of days ahead; omitted means 30.

  • Values outside 1-366 are clamped, not refused (0 or negative becomes 1, above 366 becomes 366); the result's days field shows the value used.

  • Today (the server's local date) is day 0 and always included, so days=1 covers today and tomorrow; 366 covers a full year. Behavior:

  • read-only; nothing is sent or scheduled.

  • Only contacts with a saved birthday appear; group cards never do.

  • A 29 February birthday is listed on 28 February in non-leap years. Returns:

  • {from (today), days, count, birthdays, notice}.

  • Each entry is {name, uid, date (YYYY-MM-DD of the next occurrence), days_until, has_email}, plus turns (the new age) only when the birth year is known; use the uid with contacts_get_contact for details.

  • Sorted by days_until, then name. count=0 with a note means nobody with a saved birthday falls in the window. Errors: a sign-in or connection failure raises an error; run icloud_check_health.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
daysNoHow many days ahead to look (default 30, max 366).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -{
-  "additionalProperties": true,
-  "title": "contacts_list_birthdaysDictOutput",
-  "type": "object"
-}New value: +null
  2. Addedv0.7.0

TDQS

A4.8/5.0
Behavior5/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, but the description goes far beyond: it states nothing is sent or scheduled, explains clamping behavior for the days parameter, notes that only contacts with a saved birthday appear (group cards never do), handles 29 February in non-leap years, and describes error handling via icloud_check_health. No contradiction with annotations.

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 description is well-structured with clear sections (Use when, Parameters, Behavior, Returns, Errors) and front-loads the purpose and usage. However, it is somewhat lengthy for a single-parameter list tool; while every sentence adds value, it could be trimmed slightly without losing critical information.

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

Completeness5/5

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

Given the tool's simplicity (one optional parameter), no output schema, and existing annotations, the description is complete. It covers the return structure (from, days, count, birthdays, notice), sorting, edge cases, and errors, so an agent has everything needed to call it correctly.

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 description coverage is 100% for the single 'days' parameter, so the schema already defines default 30 and max 366. The description adds meaningful edge-case semantics: omitted means 30, values outside 1-366 are clamped not refused, today is day 0, and the returned days field shows the value used. This is useful but somewhat overlaps with behavioral guidelines rather than pure parameter meaning.

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?

The description states a specific verb and resource: 'List the owner's contacts whose birthday falls within the next N days, soonest first, with the date, days until it and the age they turn.' It also explicitly distinguishes itself from siblings by naming contacts_get_contact for one person's birthday and contacts_search_contacts for finding by name.

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

Usage Guidelines5/5

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

It gives explicit when-to-use ('the owner asks whose birthday is coming up, or you are planning greetings or reminders') and when-not-to-use ('Not for one person's birthday (use contacts_get_contact) or for finding someone by name (use contacts_search_contacts)'). The alternatives are named with their conditions.

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