Skip to main content
Glama
chrischall

skylight-mcp

by chrischall
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

skylight_create_category

Add a new category or family member to the Skylight frame. Link it to a profile and chore chart, then assign an avatar or custom photo.

Instructions

Create a category / family member on the frame. Set linked_to_profile + selected_for_chore_chart to make it a full chore-chart member; pick avatar_id from skylight_list_avatars, or set a custom photo afterward with skylight_set_member_avatar.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
colorNoHex color, e.g. "#82D7DD".
labelYesDisplay name for the member/category.
frameIdNo
avatar_idNoPreset avatar id from skylight_list_avatars.
linked_to_profileNoMake this a full family-member profile (vs a basic label).
selected_for_chore_chartNoShow this member on the chore chart.

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

TDQS

A4.1/5.0
Behavior3/5

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

Annotations only indicate non-read-only and non-destructive, so the description carries most of the burden. It discloses meaningful behavioral outcomes, such as creating a full family-member profile when both booleans are set. It does not mention potential side effects like uniqueness constraints, permission requirements, or immediate visibility, so it is only moderately transparent.

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 two sentences with no filler. It front-loads the core action, then delivers the most important configuration flags and avatar workflow. Every sentence earns its place.

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?

The description plus schema covers most requirements: label, color, avatar, and the boolean pair. The main gap is frameId, which has no description in the schema and is not mentioned in the tool description, so an agent may not know how to target a specific frame. No output schema means return values don't need explanation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is high (83%), and the description adds valuable meaning beyond the individual property docs. It explains that linked_to_profile and selected_for_chore_chart must be combined to create a full chore-chart member, and it tells the agent to source avatar_id from skylight_list_avatars. This relational guidance is more than the schema provides.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the action and resource: 'Create a category / family member on the frame.' This distinguishes it from update/delete/list category siblings and other create_* tools. The verb 'Create' and the object are specific and unambiguous.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description gives practical workflow guidance: how to make a full chore-chart member by combining linked_to_profile and selected_for_chore_chart, and how to handle avatars via skylight_list_avatars or skylight_set_member_avatar. However, it does not explicitly mention when to use this tool instead of skylight_update_category or skylight_update_family_member, leaving exclusions to inference.

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