Skip to main content
Glama
chrischall

skylight-mcp

by chrischall
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

skylight_categorize_source_calendar

Assign a source calendar's events to one or more family members by providing the calendar ID and category IDs. Use this to control which family members see those events on the Skylight Calendar.

Instructions

Attribute a source calendar's events to one or more family members.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesSource-calendar id (from skylight_list_source_calendars / skylight_list_calendars).
frameIdNo
category_idsYesFamily-member category ids whose members this calendar's events are attributed to.

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. Changed4 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"
+]
    • removedInput schema / properties / id / anyOf
      Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "number"
-  }
-]
    • addedInput schema / properties / id / type
      Added value: +[
+  "string",
+  "number"
+]
  3. First observedv0.4.6

TDQS

A3.5/5.0
Behavior3/5

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

Annotations show a non-read-only, non-destructive mutation, and the description aligns by indicating an attribution writes associations. It does not reveal whether existing category assignments are replaced or how repeats behave, but the lack of destructiveHint reduces the need for strong warnings.

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?

A single sentence with no wasted words; it front-loads the action and resource and stays immediately scannable.

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?

For a three-parameter mutation with required fields documented in the schema, this is adequate for selection and basic invocation. It lacks an output description and details about frameId or overwrite semantics, so it is not fully complete for edge cases.

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

Parameters3/5

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

The schema already describes the two required parameters (id from source-calendar lists and category_ids as family-member ids), and schema coverage is 67%. The description adds no parameter-level meaning and frameId remains unexplained, but the required parameters are adequately documented.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description uses a specific verb ('Attribute') with a clear target (a source calendar's events) and recipient (one or more family members). It is not a tautology and is clearly distinct from general calendar CRUD siblings, though it does not explicitly name an alternative.

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

Usage Guidelines3/5

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

The intended use is implied by the description: use this when a source calendar's events need to be attributed to family members. However, it gives no explicit when-not-to-use guidance or alternatives, so the agent must infer selection context.

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