Skip to main content
Glama
chrischall

skylight-mcp

by chrischall
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

skylight_delete_category

Destructive

Delete a category or family member, with optional reassignment of their chores, points, and history to another category to avoid orphaning them.

Instructions

Delete a category / family member. Unless reassign_to_category_id is given, that member's chores, reward points and completion history are orphaned. Asks the user to confirm first: a confirmation prompt where the client supports one; otherwise the first call returns a preview and a confirmToken, and only a repeat call with that token proceeds (see MCP_CONFIRM_MODE). The preview names the member by label (and the destination member, if reassigning), not just the id.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYes
frameIdNo
confirmTokenNoONLY for the two-step confirmation fallback (a client without MCP elicitation). The confirmToken from this same tool's phase-1 "confirmation-required" response, passed back ONLY after the user has seen that preview and explicitly approved it in chat — never on the first call, never invented, never reused. Call again with the same arguments. Ignored when the client supports elicitation.
reassign_to_category_idNoMove this member's items to another category id instead of orphaning them.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.3.0
    • addedInput schema / properties / confirmToken
      Added value: +{
+  "description": "ONLY for the two-step confirmation fallback (a client without MCP elicitation). The confirmToken from this same tool's phase-1 \"confirmation-required\" response, passed back ONLY after the user has seen that preview and explicitly approved it in chat — never on the first call, never invented, never reused. Call again with the same arguments. Ignored when the client supports elicitation.",
+  "type": "string"
+}
  2. 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"
  3. Changed4 schema fields changedv0.7.1
    • removedInput schema / properties / id / anyOf
      Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "number"
-  }
-]
    • addedInput schema / properties / id / type
      Added value: +[
+  "string",
+  "number"
+]
    • removedInput schema / properties / reassign_to_category_id / anyOf
      Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "number"
-  }
-]
    • addedInput schema / properties / reassign_to_category_id / type
      Added value: +[
+  "string",
+  "number"
+]
  4. First observedv0.4.6

TDQS

A4.5/5.0
Behavior5/5

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

Annotations already declare destructiveHint=true and openWorldHint=true, but the description goes well beyond them: it discloses exactly what is destroyed (chores, reward points, completion history are orphaned unless reassigned), the mandatory confirmation requirement, and the two-step confirmToken fallback with its no-reuse constraint. This is exactly the kind of consequence-level detail an agent needs for a destructive mutation.

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?

Front-loaded with the core action, then consequences, then confirmation mechanics in three dense sentences with little waste. Slightly long and references an external MCP_CONFIRM_MODE constant, but every clause carries information.

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?

For a destructive 4-param tool with no output schema, the description covers consequences, the confirmation contract, and preview naming, which is strong. The unexplained frameId and the absence of any note on what the call returns leave minor gaps.

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 only 50%, and the description adds meaning the schema lacks: the consequence of omitting reassign_to_category_id (orphaning) and the lifecycle rules for confirmToken. However, 'id' and 'frameId' are never explained in either place, leaving a real gap that keeps this below 5.

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 ('Delete a category / family member') and clarifies that a 'category' here is a family member, which is not obvious from the name alone. An agent can immediately tell this apart from the many sibling delete tools (delete_chore, delete_list, delete_event) by resource.

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?

Gives real conditional guidance: use reassign_to_category_id to move items instead of orphaning, and the confirmation flow is described. It does not name a sibling alternative (e.g., update_category for non-destructive changes) or state an explicit 'do not use when', so it falls short of a 5.

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