Skip to main content
Glama
Sign In
skylight-mcp

skylight-mcp

by chrischall
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

skylight_approve_auto_creation

Approve AI-drafted calendar events by ID, converting drafts into real events on a Skylight Calendar family hub.

Instructions

Approve AI-drafted events — turns them into real calendar events.

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>",
      "ids": "<ids>"
    },
    "name": "skylight_approve_auto_creation"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesAuto-creation intent id.
idsYesDraft event ids to approve into real events.
frameIdNo

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

TDQS

B3.2/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 write nature and safety profile are covered structurally. The description adds that drafts are converted into real calendar events, which is useful semantic context, but it omits reversibility (an undo sibling exists), whether repeated approvals are idempotent, and any auth/permission requirements.

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, front-loaded sentence with no filler; the core action and outcome come first. It is a touch terse given the gaps in usage and parameter explanation, but there is no wasted text.

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?

There is no output schema, so the description would ideally say what the agent gets back or what state changes occur. For a mutation tool with annotations covering safety, the description is minimally adequate but leaves the intent-id/draft-id workflow and undo relationship unclear.

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?

Schema coverage is 67%: 'id' (intent id) and 'ids' (draft event ids) are both described in the schema, but 'frameId' is undocumented. The description adds nothing about the id vs ids relationship, so it neither compensates nor detracts; the baseline of 3 fits a moderately documented schema.

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 ('approve AI-drafted events') and clarifies the effect ('turns them into real calendar events'), which separates it from read-only siblings like skylight_list_auto_creation_drafts. It does not explicitly distinguish itself from the closely related skylight_undo_auto_creation, but the action direction is unmistakable.

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?

No guidance on when to use this tool versus alternatives such as skylight_get_auto_creation_intent, skylight_list_auto_creation_drafts, or skylight_undo_auto_creation. There is no mention of prerequisites (e.g., needing a prior intent id) or when approval is appropriate.

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