Skip to main content
Glama
chrischall

skylight-mcp

by chrischall
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

skylight_create_event

Create a calendar event on a Skylight frame with details like title, schedule, recurrence, location, and guest emails.

Instructions

Create a calendar event on a Skylight frame.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
rruleNoiCalendar RRULE for recurrence.
all_dayNo
ends_atNoISO 8601 end.
frameIdNo
summaryYesEvent title.
locationNo
timezoneNo
starts_atNoISO 8601 start.
descriptionNo
category_idsNoFamily-member category ids to assign the event to (see skylight_list_categories / skylight_resolve_member).
invited_emailsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. 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"
  2. Changed2 schema fields changedv0.7.1
    • removedInput schema / properties / category_ids / items / anyOf
      Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "number"
-  }
-]
    • addedInput schema / properties / category_ids / items / type
      Added value: +[
+  "string",
+  "number"
+]
  3. First observedv0.4.6

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already indicate this is a write operation (readOnlyHint=false) and non-destructive (destructiveHint=false). The description adds no further behavioral context—no side effects, permissions, or constraints. It neither contradicts annotations nor enriches transparency, staying at a baseline score.

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?

The description is a single, crisp sentence with no superfluous words. It front-loads the verb and resource, making it instantly scannable. Although the tool is complex, the statement itself achieves conciseness without sacrificing clarity.

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

Completeness2/5

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

With 11 parameters, no output schema, and low schema coverage, the description is severely incomplete. It omits how to specify event timing, recurrence, target frame, or any return behavior. An agent would lack essential information to invoke the tool correctly, especially given the numerous undocumented parameters.

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 only 45%, leaving several parameters undocumented (all_day, frameId, location, timezone, description, invited_emails). The description provides zero parameter information, failing to compensate for the schema gaps. It does not clarify required vs. optional fields or their 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 clear verb ('Create'), resource ('calendar event'), and target ('on a Skylight frame'). It is unambiguous and distinguishes this tool from the update/delete/list siblings by its explicit action and resource, making it immediately identifiable.

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

Usage Guidelines2/5

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

The description provides no guidance on when to use this tool versus alternatives. It does not mention conditions for creating a new event, prerequisites, or when to prefer this over update/delete/list tools. An agent must rely solely on the tool name and sibling list.

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