Skip to main content
Glama
chrischall

skylight-mcp

by chrischall
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

skylight_create_category

Create a category or family member on a Skylight frame, then link it to a profile, add it to the chore chart, or assign an avatar.

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.4/5.0
Behavior4/5

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

Annotations already declare a non-destructive write (readOnlyHint=false, destructiveHint=false, openWorldHint=true), so the safety profile is covered. The description adds real behavioral context beyond that: that linked_to_profile + selected_for_chore_chart jointly upgrade the created entity, and that avatars can be set at creation or deferred to a later call. No permission or return-value detail is given, which keeps it out of the top band.

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?

Two sentences, front-loaded with the core action before the parameter configuration guidance. Every clause carries information: entity equivalence, flag combo, avatar source, avatar fallback. No filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

No output schema exists, and the description does not say what the call returns (e.g. the new category's id) or how frameId defaults when omitted. For a 6-parameter creation tool with high schema coverage, what is present is enough to call it correctly, but the return/identity gap keeps it short of complete.

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 description coverage is 83%, so the baseline is a 3. The description earns above baseline by explaining the composite effect of two booleans that the schema documents only in isolation, and by naming the source tool for avatar_id. color, label and frameId receive no added meaning in the description.

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?

States a specific verb and resource ('Create a category / family member on the frame'), and crucially resolves the naming ambiguity by equating 'category' with 'family member', which is exactly what separates this tool from skylight_update_family_member and skylight_resolve_member. An agent can tell what it produces without opening the schema.

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?

It routes the agent to sibling tools for adjacent steps ('pick avatar_id from skylight_list_avatars', 'set a custom photo afterward with skylight_set_member_avatar') and explains the flag combination that produces a full chore-chart member. It does not state when to prefer this over skylight_update_family_member or skylight_update_category, so the exclusion side is implied rather than explicit.

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