Skip to main content
Glama
chrischall

skylight-mcp

by chrischall
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

skylight_clear_list

Destructive

Delete all items from a Skylight Calendar list permanently, with a confirmation preview to prevent accidental deletion. Empty lists need no confirmation.

Instructions

Remove all items from a list — permanent. Asks the user to confirm first: a confirmation prompt where the client supports one; otherwise the first call returns a preview and a confirmToken, and only a repeat call with that token proceeds (see MCP_CONFIRM_MODE). The preview lists every item that would go, by label, and the token binds that exact set. An already-empty list needs no confirmation.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
listIdYes
frameIdNo
confirmTokenNoONLY for the two-step confirmation fallback (a client without MCP elicitation). The confirmToken from this same tool's phase-1 "confirmation-required" response, passed back ONLY after the user has seen that preview and explicitly approved it in chat — never on the first call, never invented, never reused. Call again with the same arguments. Ignored when the client supports elicitation.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.3.0
    • addedInput schema / properties / confirmToken
      Added value: +{
+  "description": "ONLY for the two-step confirmation fallback (a client without MCP elicitation). The confirmToken from this same tool's phase-1 \"confirmation-required\" response, passed back ONLY after the user has seen that preview and explicitly approved it in chat — never on the first call, never invented, never reused. Call again with the same arguments. Ignored when the client supports elicitation.",
+  "type": "string"
+}
  2. 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"
  3. First observedv0.4.6

TDQS

A3.9/5.0
Behavior5/5

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

Annotations already declare destructiveHint=true, but the description goes far beyond that: it states permanence, describes the two confirmation paths (elicitation vs. confirmToken fallback), explains that the preview enumerates affected items by label, and notes the token binds that exact set. It also carves out the empty-list case, all of which meaningfully de-risks invocation.

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?

Front-loaded with the core destructive action before any mechanics, and each subsequent sentence carries operational weight. It is dense but not padded; the parenthetical reference to MCP_CONFIRM_MODE is a slight external dependency rather than self-contained prose.

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 destructive mutation with no output schema and 33% parameter coverage, the description covers the highest-risk aspects (permanence, confirmation, preview contents). It stops short of describing the success response or frameId scoping, but the critical decision path is complete.

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 description coverage is only 33%. The description usefully clarifies confirmToken's role and when it must not be used, but frameId receives no explanation in either the description or the schema, and listId's format is unstated. Compensation is partial, not full.

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 first sentence gives a specific verb, resource, and scope ('Remove all items from a list — permanent'), which is clearly distinct from sibling operations like delete_list (removes the list itself) or delete_list_item (single item). However, it never names or contrasts those siblings, so the agent must infer the boundary between clearing and deleting.

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 description spends its bulk on the confirmation mechanics rather than on when to choose this tool over skylight_delete_list_items or skylight_delete_list. Operational context (confirmation flow, empty-list exemption) is provided, but there is no explicit alternative-selection guidance.

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