Skip to main content
Glama
chrischall

skylight-mcp

by chrischall
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

skylight_delete_category

Destructive

Delete a category or family member, reassigning their chores and rewards to another category to prevent data loss. Requires confirmation before removal.

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 flag the tool as destructive, but the description goes well beyond that by disclosing that chores, reward points, and completion history get orphaned, and by detailing the confirmation fallback with a preview and confirmToken. This is exactly the kind of behavioral context an agent needs before calling a destructive tool.

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?

The description is front-loaded with the core action and then moves to consequences and confirmation behavior. Every sentence contributes, though the parenthetical about confirmation modes makes the middle sentence slightly dense. No filler is present.

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?

Given there is no output schema, the description does a good job of explaining what the first call returns (preview and confirmToken) and how to proceed. It omits details about the success response of the final call and leaves frameId ambiguous, but for a destructive tool with confirmation, the essential operating context is covered.

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 50% because id and frameId lack descriptions-newline while confirmToken and reassign_to_category_id have them. The description compensates by explaining the consequence of omitting reassign_to_category_id and by clarifying how confirmToken is used in the two-step flow. The frameId parameter remains unexplained, but the description adds meaningful value for the parameters that matter most in a destructive delete scenario.

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 opens with a specific verb and resource: 'Delete a category / family member.' It clearly identifies the operation and the subject, and stands apart from siblings like update_category or create_category by being explicitly a deletion. The mention of 'family member' additionally disambiguates the category concept from other category-like tools.

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 provides clear context by stating the conditional behavior: unless reassign_to_category_id is given, related data is orphaned. It also explains the two-step confirmation flow, which is essential for correct invocation. It does not explicitly name alternatives such as update_category for non-destructive changes, so it stops short of full when-to-use-versus-alternatives guidance.

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