Skip to main content
Glama
epinethrone

icloud-mcp

by epinethrone
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

icloud_get_time

Read-only

Retrieve current date, weekday, and time in a specified IANA timezone. Use before proposing, booking, or resolving relative dates.

Instructions

Get the current date, weekday and clock time in the owner's timezone, or in another IANA timezone.

Use when: before proposing, booking or resolving relative dates ('tomorrow', 'next Friday'), since you cannot know today's date otherwise. Not needed right after calendar_list_events or calendar_find_free_time, whose results already carry 'now'; not for open time (use calendar_find_free_time). Parameters: timezone only chooses the zone the clock is shown in; it changes no setting. Give an IANA Area/City name such as 'America/New_York', or 'UTC'. An offset such as '+02:00' or an abbreviation such as 'PST' is refused. Omitted or '' means the owner's DEFAULT_TIMEZONE (UTC when unset); call it without one to learn the owner's zone. Behavior: read-only and local: it reads the server clock and contacts no iCloud service, so it works even when iCloud is down. It is refused while the owner has paused the server. Returns: {now (ISO 8601 with offset, to the second), date (YYYY-MM-DD), weekday (English name, e.g. Monday), time (HH:MM, 24-hour), timezone (the IANA name used)}. Errors: an unknown name raises "Unknown timezone ..."; retry with a valid IANA name or omit it.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
timezoneNoIANA timezone for times without an offset, e.g. 'Europe/Berlin'; default the owner's.

Schema Changelog

Changes observed during successful MCP inspections.

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

TDQS

A4.9/5.0
Behavior5/5

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

Annotations only supply readOnlyHint and openWorldHint, so the description carries real weight and delivers: it reads the server clock, makes no iCloud call, therefore works during an iCloud outage, but is refused while the server is paused. It also documents the error surface ('Unknown timezone ...') and the exact return shape, none of which the annotations provide.

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?

Front-loaded with the core action, then segmented into Use when / Parameters / Behavior / Returns / Errors so an agent can scan to the relevant block. It is long, but every sentence carries decision-relevant information (refusal conditions, defaults, outage behavior) with no filler.

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?

With no output schema, the description supplies the full return contract (field names, formats, units, 24-hour clock, ISO 8601 with offset) and the error contract. Combined with the default-timezone and paused-server behavior, nothing an agent needs to call this correctly is missing.

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 already 100%, so the baseline is 3, but the description goes beyond the schema: it specifies IANA Area/City format, states that offsets ('+02:00') and abbreviations ('PST') are refused, and clarifies that omission or '' yields the owner's DEFAULT_TIMEZONE, with a bare call as the way to discover the owner's zone. That is meaningful added semantics over the schema's one-line default note.

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 ('Get the current date, weekday and clock time') plus the scoping modifier of timezone choice. It explicitly distinguishes itself from calendar_list_events, calendar_find_free_time and calendar_get_event, so an agent can route correctly without opening any schema.

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?

Gives an explicit trigger ('before proposing, booking or resolving relative dates'), an explicit non-use case ('Not needed right after calendar_list_events or calendar_find_free_time, whose results already carry now'), and names the alternative for a related need ('not for open time (use calendar_find_free_time)'). This is textbook when/when-not/alternative guidance.

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