Skip to main content
Glama
Sign In
icloud-calendar-mcp

icloud-calendar-mcp

by hrsather
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

get_event

Retrieves a single calendar event by UID, returning the full series and RRULE for recurring events so you can inspect its details.

Instructions

Get one event by UID. For a recurring event this returns the series, including its RRULE.

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": {
      "uid": "<uid>"
    },
    "name": "get_event"
  }
}

Input Schema

NameRequiredDescriptionDefault
uidYes
calendarNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

A3.8/5.0
Behavior3/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 usefully discloses that a recurring event returns the series including its RRULE, but it does not explicitly state read-only behavior, permissions, calendar default behavior, or not-found behavior.

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?

Two short, front-loaded sentences with no filler. The core lookup is stated first and the recurring-event caveat follows logically.

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

Completeness3/5

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

The output schema covers return shape, and the description covers the core single-event retrieval plus recurrence behavior. However, with no annotations and an unexplained optional calendar parameter, it is only adequate rather than complete for correct invocation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must explain both parameters. It only ties the UID to event lookup and never explains the optional 'calendar' parameter, its default, or its semantics, leaving a significant gap.

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 one event by UID.' The singular retrieval scope distinguishes it from list_events and the mutation siblings, and the recurring-event note clarifies its scope further.

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?

Gives clear context: use it to retrieve a single event when the UID is known, and sets expectations for recurring events. It does not explicitly name an alternative such as list_events or state when not to use it, so it falls short of a 5.

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