Skip to main content
Glama
chrischall

skylight-mcp

by chrischall
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

skylight_update_frame

Destructive

Update Skylight frame display and sleep settings, including brightness, slideshow, and public access. Changes apply directly except public sharing, which requires confirmation.

Instructions

Update Skylight frame display/sleep settings. Setting open_to_public:true makes the frame publicly reachable, so that one change 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). Every other setting applies directly.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
frameIdNo
wakes_atNo
sleeps_atNoTime the frame sleeps, e.g. "22:00".
brightnessNo
show_heartNo
blur_effectNo
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.
show_captionNo
side_by_sideNo
open_to_publicNo
slideshow_speedNo
slideshow_styleNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv1.3.0
    • removedInput schema / properties / confirm
      Removed value: -{
-  "description": "Must be true to proceed. Without this, the tool returns a preview.",
-  "type": "boolean"
-}
    • 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.1.3
    • addedInput schema / properties / confirm
      Added value: +{
+  "description": "Must be true to proceed. Without this, the tool returns a preview.",
+  "type": "boolean"
+}
  3. 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"
  4. First observedv0.4.6

TDQS

B3.4/5.0
Behavior4/5

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

Annotations declare destructiveHint=true and openWorldHint=true, and the description goes beyond them by explaining exactly which change is sensitive (open_to_public making the frame publicly reachable) and the confirm/preview-token protocol. That is meaningful added context, though it does not describe reversibility or return shape.

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 purpose and then the one notable exception, with no filler sentences. The confirmation-flow sentence is dense but every clause carries needed information.

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

Completeness3/5

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

For a 12-parameter destructive mutation tool with no output schema, the description usefully covers the riskiest behavior (public exposure + confirmation) but leaves the bulk of the parameters and the response behavior unexplained, so an agent still faces gaps.

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

Parameters2/5

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

Schema description coverage is only 17% across 12 parameters, so the description must compensate, but it only clarifies the semantics of open_to_public and confirmToken. Values like wakes_at, sleeps_at, brightness, slideshow_speed, and the show_* booleans get no added meaning beyond their names.

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 opening sentence gives a specific verb and resource ('Update Skylight frame display/sleep settings'), which distinguishes it from siblings like skylight_rename_frame and skylight_update_profile. It does not explicitly name an alternative tool, so it falls short of a 5.

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

Usage Guidelines3/5

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

It describes the special two-step confirmation flow for open_to_public and states that 'every other setting applies directly', which is useful operational guidance. However, it gives no guidance on when to choose this tool over other frame-related siblings (get_frame, rename_frame), so usage context is only implied.

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