Skip to main content
Glama
chrischall

skylight-mcp

by chrischall
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

skylight_update_category

Update a Skylight Calendar category by renaming or recoloring it, or promote a label to a linked family-member profile.

Instructions

Update a category — rename/recolor, or convert a label into a family-member profile (linked_to_profile).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesCategory id.
colorNoHex color.
labelNoDisplay name.
frameIdNo
avatar_idNo
linked_to_profileNoSet true to convert a basic label into a full family-member profile.
selected_for_chore_chartNo

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

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false and destructiveHint=false, so the mutation/safety profile is partly covered. The description adds that setting linked_to_profile promotes a label into a full family-member profile, a meaningful state change, but it does not disclose reversibility, permissions, or what happens to existing category-scoped data. That added context partly duplicates the schema's own description of linked_to_profile.

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 primary verb and resource come first and the two operating modes follow. Slightly dense with the parenthetical, but nothing is wasted.

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?

For a 7-parameter mutation tool with no output schema and 43% of parameters undocumented, the description leaves real gaps: no explanation of frameId, avatar_id, or selected_for_chore_chart, and no statement of permissions or side effects. It is minimally viable but not 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 coverage is 57%, so three parameters (frameId, avatar_id, selected_for_chore_chart) are undocumented in both schema and description. The description's rename/recolor and linked_to_profile mentions map onto parameters that the schema already describes, adding little new meaning.

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 ('Update a category') and enumerates the two operative modes (rename/recolor vs. convert a label into a family-member profile). This distinguishes it from skylight_create_category and skylight_delete_category, though it never names those siblings explicitly.

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 two modes ('rename/recolor' and 'convert a label into a family-member profile') imply when each field group applies, but there is no explicit guidance on when to choose this tool over skylight_create_category or skylight_delete_category, nor any stated prerequisites.

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