Skip to main content
Glama
chrischall

skylight-mcp

by chrischall
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

skylight_delete_album

Destructive

Remove a photo album from your Skylight Calendar family hub using its album ID.

Instructions

Delete a photo album.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYes
frameIdNo

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

TDQS

C2.6/5.0
Behavior2/5

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

Annotations already flag destructiveHint=true, so the description needed to add behavioral context such as whether photos are also deleted or whether frameId scopes the deletion. The bare 'delete' verb adds nothing beyond the tool name and provides no additional transparency.

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 a single short sentence with no filler and correctly front-loads the action. It is almost too sparse to be useful, but structurally it is efficient and wastes no words.

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

Completeness2/5

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

With a required id and optional frameId, the description leaves ambiguous whether the deletion is global or frame-scoped, whether frameId is required in certain cases, and what happens to contained photos. Without parameter docs or an output schema, an agent cannot confidently invoke this tool in non-trivial contexts.

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

Parameters1/5

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

Schema description coverage is 0% and the description provides no parameter meanings. The id parameter is only inferable from the tool name, while frameId's purpose is entirely undocumented. With no compensation in the description, parameter semantics are missing.

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

Purpose4/5

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

The description states a specific verb and resource: 'Delete a photo album.' This clearly separates it from create/update/remove-from-album tools by naming the resource. It does not, however, explicitly differentiate from other delete tools or mention scoping details.

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

Usage Guidelines2/5

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

No guidance is given about when to use this tool instead of alternatives. There is no mention of frameId, album ownership, or the relationship to tools like skylight_remove_from_album or skylight_set_device_album, leaving usage context entirely 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