Related Servers

Tools are organized per resource (events, chores, lists, meals, rewards, photos), and descriptions do real work to separate near-duplicates (e.g. skylight_delete_message vs skylight_delete_messages, complete_chore vs complete_chore_instance). However, with 115 tools there are genuine boundary problems: delete_list_item / delete_list_items / clear_list / delete_list, list_categories vs list_frame_members vs resolve_member, list_auto_creation_drafts vs list_auto_creation_items, and create_chore vs create_recurring_chore all require careful reading to select correctly.

Nearly everything follows the skylight_ prefix + verb_noun pattern (list_events, create_event, update_chore, delete_recipe), which is highly predictable. Minor deviations: skylight_healthcheck has no verb_noun shape, and there is inconsistent singular/plural pairing (delete_message vs delete_messages, delete_list_item vs delete_list_items).

The domain (a family smart-display hub: calendars, photos, lists, chores, meals, rewards, users, devices, AI drafts) is genuinely broad, so a large surface is defensible. But 115 tools is far past practical scope — many are niche or single-purpose (healthcheck, upload_slots, resolve_member, list_avatars, list_recent_invited_emails), and the cognitive load on an agent choosing among them is severe.

Coverage is impressive: full CRUD across events, lists, chores, meals, recipes, rewards, albums, users, plus settings, AI draft lifecycle, and upload plumbing. Gaps are minor — no standalone get_list or get_album, no get_chore by id (only search/list), and nudges are read-only (list_nudges with no create/update/delete).