skylight-mcp

skylight_create_source_calendar

Create a calendar source from raw provider attributes to set up advanced calendar syncs. Supply provider-specific attributes and an optional frame ID.

Instructions

Create a source calendar from raw provider attributes (advanced).

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": {
      "attributes": "<attributes>"
    },
    "name": "skylight_create_source_calendar"
  }
}

Input Schema

Name	Required	Description	Default
`frameId`	No
`attributes`	Yes	Provider-specific source-calendar attributes.

Schema Changelog

Changes observed during successful MCP inspections.

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

C2.9/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, and openWorldHint=true, so the mutation/safety profile is covered. The description adds only that input is raw provider attributes (low-level/advanced), which is modest context beyond the structured hints and omits what happens on failure or what data must be supplied.

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?

A single short, front-loaded sentence with no filler. The parenthetical qualifier is slightly vague but costs little space.

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?

For a mutation tool taking a required free-form nested object and shipping no output schema, the description leaves key gaps: what 'raw provider attributes' contain, auth/scope needs, and how to choose it over add_webcal/link_apple_calendar. It is not adequate 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?

At 50% schema coverage, the description should compensate but does not: 'raw provider attributes' restates the attributes field, while frameId is undocumented in both schema and description. No format, examples, or required provider keys are given for the nested attributes object.

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?

States a specific verb+resource: 'Create a source calendar'. The 'from raw provider attributes' clause clarifies the input mode, and it can be distinguished from list/delete/categorize source-calendar siblings. It does not, however, differentiate itself from other calendar-creation siblings like skylight_add_webcal or skylight_link_apple_calendar.

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 '(advanced)' tag hints at caution but gives no explicit when-to-use, when-not-to-use, or alternative routing (e.g., add_webcal or link_apple_calendar for the common cases). An agent must infer applicability entirely.

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

Deploy Server