skylight-mcp

skylight_get_event

Read-only

Retrieve a single Skylight calendar event by id, including the family members it belongs to. Searches a date window automatically, with date_min and date_max to look outside the default year.

Instructions

Get one calendar event by id (an id from skylight_list_events), including the family members it belongs to in categories. Skylight has no single-event endpoint, so this searches a date window: a recurring-occurrence id ({master}-{epoch}) is found around its own date automatically; for other ids the default window is a year either side of today — pass date_min/date_max to search elsewhere.

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": {
      "id": "<id>"
    },
    "name": "skylight_get_event"
  }
}

Input Schema

Name	Required	Description
`id`	Yes
`frameId`	No
`date_max`	No	YYYY-MM-DD upper bound of the search window.
`date_min`	No	YYYY-MM-DD lower bound of the search window (see description for the default).

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedv1.4.8Nov 3, 2026

addedInput schema / properties / date_max

Added value: +{
+  "description": "YYYY-MM-DD upper bound of the search window.",
+  "type": "string"
+}

addedInput schema / properties / date_min

Added value: +{
+  "description": "YYYY-MM-DD lower bound of the search window (see description for the default).",
+  "type": "string"
+}

Changed1 schema field changedv1.0.1Sep 19, 2026

changedInput schema / $schema

Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"

First observedv0.4.6Jul 30, 2026

TDQS

A4.6/5.0

Behavior4/5

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

The annotations only declare readOnlyHint and openWorldHint; the description adds the crucial non-obvious behavior that there is no single-event endpoint and this is a date-window search with a one-year-either-side default. That is exactly the kind of hidden cost an agent needs. It stops short of saying what happens when the search misses (empty result vs. error) or how many matches can come back.

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?

Three sentences, front-loaded with the purpose, then the id provenance, then the window mechanics. Every clause carries information an agent would otherwise have to discover by failure; nothing is redundant with the schema.

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 four-parameter read tool with no output schema, the description covers the hard part: why a 'get by id' needs a date window and how to widen it. The residual gap is `frameId`, undocumented anywhere, plus no note on behavior when no match is found.

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 50%, so the description must carry weight for `id` and `frameId`. It does explain the id's provenance and the `{master}-{epoch}` recurring format, and it reinforces the default for date_min/date_max. `frameId` remains entirely unexplained in both schema and description, which keeps this off a 5.

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 first clause states a specific verb and resource ('Get one calendar event by id'), names where the id comes from (skylight_list_events), and specifies the payload ('including the family members it belongs to in `categories`'). That distinguishes it cleanly from skylight_list_events and the other event-mutation siblings.

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 routes the agent to skylight_list_events as the id source and explicitly states when the default window applies versus when to pass date_min/date_max. It even carves out the one exception (recurring-occurrence ids are resolved around their own date automatically), so no inference is needed.

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

Deploy Server