Skip to main content
Glama
chrischall

skylight-mcp

by chrischall
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

skylight_link_apple_calendar

Link an Apple/iCloud calendar to your Skylight frame so events appear on the display. Uses a secure app-specific password from the server environment and requires your confirmation before granting access.

Instructions

Link an Apple/iCloud calendar to the frame. The app-specific password is read from the server's SKYLIGHT_APPLE_APP_PASSWORD environment variable — it is never a tool argument, so it never passes through the model or the transcript. Linking hands Skylight persistent access to that iCloud account's calendars, so it asks the user to confirm first: a confirmation prompt where the client supports one; otherwise the first call returns a preview and a confirmToken, and only a repeat call with that token proceeds (see MCP_CONFIRM_MODE). The preview names the Apple ID and frame and fingerprints (never shows) the password.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
emailNoApple ID email. Defaults to SKYLIGHT_APPLE_ID from the server's environment.
frameIdNo
confirmTokenNoONLY for the two-step confirmation fallback (a client without MCP elicitation). The confirmToken from this same tool's phase-1 "confirmation-required" response, passed back ONLY after the user has seen that preview and explicitly approved it in chat — never on the first call, never invented, never reused. Call again with the same arguments. Ignored when the client supports elicitation.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv1.3.0
    • removedInput schema / properties / app_specific_password
      Removed value: -{
-  "description": "An app-specific password generated at appleid.apple.com (NOT your normal Apple password).",
-  "type": "string"
-}
    • addedInput schema / properties / confirmToken
      Added value: +{
+  "description": "ONLY for the two-step confirmation fallback (a client without MCP elicitation). The confirmToken from this same tool's phase-1 \"confirmation-required\" response, passed back ONLY after the user has seen that preview and explicitly approved it in chat — never on the first call, never invented, never reused. Call again with the same arguments. Ignored when the client supports elicitation.",
+  "type": "string"
+}
    • changedInput schema / properties / email / description
      Previous value: -"Apple ID email."New value: +"Apple ID email. Defaults to SKYLIGHT_APPLE_ID from the server's environment."
    • removedInput schema / required
      Removed value: -[
-  "email",
-  "app_specific_password"
-]
  2. Changed1 schema field changedv1.0.1
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
  3. First observedv0.4.6

TDQS

A4.8/5.0
Behavior5/5

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

Annotations only indicate non-read-only and non-destructive, but the description goes far beyond: it explains that linking grants persistent access, requires user confirmation, previews the Apple ID and frame, fingerprints the password, and only proceeds with a repeat call using the confirmToken. It also explains the MCP_CONFIRM_MODE behavior, giving the agent a full picture of side effects and prerequisites.

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 a single dense paragraph, packing a lot of information. It is somewhat long but every sentence adds value—no fluff. The key points (link action, password handling, confirmation) are front-loaded, though the confirmToken details come later. Slightly more structure (breaking into bullets) would improve scannability, but it is acceptable.

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?

For a tool with 3 optional parameters and no output schema, the description is remarkably complete. It explains the authentication mechanism, the confirmation flow, the fallback token usage, and the preview content. An agent has everything needed to invoke it correctly and can even handle edge cases like clients without elicitation support.

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?

The schema covers the email and confirmToken parameters, but the description adds critical context: email defaults to an environment variable, and confirmToken is only for two-step fallback with explicit do-not-use rules. This goes beyond the schema's basic descriptions, making the parameter semantics much clearer.

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 clearly states the action ('Link an Apple/iCloud calendar to the frame') and the specific resource (iCloud calendar). It also includes distinctive details about the password handling and confirmation flow, setting it apart from calendar management siblings like skylight_add_webcal or skylight_create_source_calendar.

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?

The description explicitly explains when to use this tool (linking an Apple/iCloud calendar) and gives concrete usage rules: the app-specific password is read from the server environment, never passed as an argument, and a confirmation step is required. It also explains the two-step fallback with confirmToken for clients without elicitation support, which is crucial for correct usage.

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