Skip to main content
Glama
chrischall

skylight-mcp

by chrischall
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

skylight_create_chore

Create a chore on your Skylight frame by entering a summary and category ID. Optionally add start date, description, and reward points to assign tasks to family members.

Instructions

Create a chore on a Skylight frame.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
startNoYYYY-MM-DD start date.
frameIdNo
summaryYesChore title.
category_idYesCategory / family-member id the chore belongs to (required). Get ids from skylight_list_categories.
descriptionNo
reward_pointsNoReward points/stars for completing.

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 already indicate this is a mutating, non-destructive operation, so the bar for additional behavioral disclosure is lower. However, the description adds no context beyond 'create': it does not mention side effects, whether a frameId is required in practice, how categories/members are assigned, or what happens on success. No contradiction with annotations.

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?

The description is a single, front-loaded sentence with no filler or redundant phrasing. It states the action and target resource immediately and does not waste the agent's attention.

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 6-parameter create operation with no output schema, this description is too thin. It omits usage context, optional parameter behavior, required category resolution, and any sense of what a successful call returns. The agent must rely entirely on the schema and sibling tool names to understand the full context.

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 contributes no parameter-level meaning. The schema covers only 67% of parameters, and frameId and description are undocumented in both the schema and the description. Useful guidance like 'Get ids from skylight_list_categories' exists only in the schema, not in the tool description, so the description fails to compensate for the coverage gaps.

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 uses a specific verb and resource: 'Create a chore on a Skylight frame.' This clearly distinguishes it from sibling tools like skylight_create_task or skylight_create_reward at a basic level. It does not explicitly contrast it with skylight_create_recurring_chore, but the core purpose is unambiguous.

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 guidance on when to use this tool versus alternatives such as skylight_create_task or skylight_create_recurring_chore. The only usage signal is the tool's name and description restating that it creates a chore, without any context or exclusions.

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