Skip to main content
Glama
chrischall

skylight-mcp

by chrischall
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

skylight_update_chore

Destructive

Update an existing chore's details, schedule, or recurrence. For recurring chores, choose this occurrence or the whole series, with confirmation before broad changes.

Instructions

Update a chore. apply_to 'this_and_future' or 'all' 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).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYes
startNo
frameIdNo
summaryNo
apply_toNoFor recurring chores: which occurrences to update.
emoji_iconNo
recurrenceNoiCalendar RRULE without the "RRULE:" prefix; edits the whole series.
start_timeNo
category_idNo
descriptionNo
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.
reward_pointsNo
recurring_untilNoISO datetime the recurrence ends.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv1.3.0
    • removedInput schema / properties / confirm
      Removed value: -{
-  "description": "Must be true to proceed. Without this, the tool returns a preview.",
-  "type": "boolean"
-}
    • 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. Changed1 schema field changedv0.8.1
    • addedInput schema / properties / confirm
      Added value: +{
+  "description": "Must be true to proceed. Without this, the tool returns a preview.",
+  "type": "boolean"
+}
  4. Changed2 schema fields changedv0.7.1
    • removedInput schema / properties / category_id / anyOf
      Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "number"
-  }
-]
    • addedInput schema / properties / category_id / type
      Added value: +[
+  "string",
+  "number"
+]
  5. First observedv0.4.6

TDQS

B3/5.0
Behavior4/5

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

Annotations declare destructiveHint=true and openWorldHint=true but not the confirmation requirement; the description adds substantial context on the two-phase confirmation flow (native prompt where supported, otherwise preview + confirmToken repeat call, referencing MCP_CONFIRM_MODE). This is real behavioral disclosure beyond the annotations, though it omits reversibility and 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.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The core purpose is front-loaded correctly in the first three words, but the remainder is a single dense, semicolon-chained sentence about confirmToken mechanics that is more verbose than needed. It is functional but not tightly structured.

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 13-parameter destructive mutation with no output schema and low schema coverage, the description should explain the update surface and any auth/permission constraints. It instead covers only the confirmation edge case, leaving an agent unable to know what a typical call should contain.

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 31% across 13 parameters, so the description carries a heavy compensation burden. It clarifies apply_to and reiterates confirmToken (already well documented in the schema), but says nothing about id, start, frameId, summary, recurrence, category_id, reward_points, or the other undocumented fields.

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 opening sentence gives a specific verb+resource ('Update a chore') that is immediately distinguishable from create/delete/complete siblings. However, the bulk of the description pivots to confirmation mechanics rather than elaborating the update scope, and it never names what can be updated or which sibling to prefer.

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?

It explains the confirm flow for specific apply_to values but gives no guidance on when to use update_chore versus skylight_complete_chore, skylight_delete_chore, or skylight_update_task, nor any prerequisites for updating. Usage is only implied by the parameter discussion.

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