Skip to main content
Glama
chrischall

skylight-mcp

by chrischall
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

skylight_complete_chore_instance

Complete a specific occurrence of a recurring chore by date, assigning a member for shared chores and a time for routines with multiple daily instances.

Instructions

Mark a specific occurrence of a recurring chore complete.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYes
frameIdNo
category_idNoOnly for an up-for-grabs/shared chore: which member completed it. Omit for a normally-assigned chore (sending it 422s).
instance_dateYesYYYY-MM-DD occurrence date (required).
instance_timeNoHH:MM — only for a time-of-day routine with multiple daily occurrences.

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. 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"
+]
  3. First observedv0.4.6

TDQS

C2.8/5.0
Behavior2/5

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

Annotations declare readOnlyHint=false and destructiveHint=false, so the mutation is already implied. The description itself adds no detail about side effects, reversibility via uncomplete, idempotency, or failure behavior. The 'specific occurrence' qualifier is the only meaningful behavioral context, but it is not sufficient.

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, front-loaded sentence with no filler. It communicates the core operation immediately and does not repeat the tool name or schema details.

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?

The tool has 5 parameters, conditional behavior for category_id and instance_time, no output schema, and minimal annotations. The description is too thin to fully contextualize the call: it omits the role of id/frameId, when this tool is preferred over skylight_complete_chore, and what happens after completion. An agent would need to infer several important details.

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?

The description adds no parameter-level meaning beyond 'specific occurrence.' The schema covers category_id and instance_date well, but id and frameId are undocumented, and the description does not clarify them. With only 60% schema coverage and no compensating explanation, an agent may not know what `id` refers to or how `frameId` is used.

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 states a clear action ('Mark') and a specific resource ('a specific occurrence of a recurring chore'). It mostly distinguishes itself from the sibling skylight_complete_chore by emphasizing 'specific occurrence,' though it does not explicitly contrast the two.

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?

There is no explicit when-to-use or when-not-to-use guidance. The phrase 'specific occurrence of a recurring chore' implies this is for recurring instances, but it does not say when to use skylight_complete_chore instead, how this differs from skylight_uncomplete_chore, or what prerequisites exist.

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