Skip to main content
Glama
chrischall

skylight-mcp

by chrischall
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

skylight_update_frame

Update Skylight frame display and sleep settings like brightness, slideshow speed, and schedule. Public visibility changes require user confirmation before applying.

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

A3.5/5.0
Behavior4/5

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

Annotations are minimal (readOnlyHint: false, destructiveHint: false), so the description carries the burden. It discloses the two-step confirmation flow for open_to_public and clarifies that all other settings apply directly. This adds significant behavioral context beyond the schema and annotations, though it does not cover other potential behaviors like immediate application or side effects.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is two sentences, but the second sentence is long and dense, mixing confirmation flow and fallback behavior. The core purpose is front-loaded, but the structure could be improved by separating the confirmation behavior into a distinct note. It is not overly verbose, but the complexity reduces clarity.

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?

Given 12 parameters, no output schema, and low schema coverage, the description is incomplete. It explains the confirmation flow but does not cover many parameters, nor does it mention return values, required fields (none are required, but frameId is likely essential), or any side effects. An agent would need to guess at the semantics of most fields, making this insufficient for reliable invocation.

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%, so the description must compensate. It explains the behavior of open_to_public but does not clarify the meaning or format of most other parameters (frameId, wakes_at, brightness, show_heart, etc.). The phrase 'display/sleep settings' gives a hint, but it does not provide concrete guidance for each parameter. The confirmToken is already described in the schema, so the description adds no extra value there.

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 clearly states the verb ('Update'), the resource ('Skylight frame'), and the specific domain ('display/sleep settings'). This distinguishes it from sibling tools like skylight_rename_frame or skylight_set_device_album, which operate on other aspects. The purpose is unambiguous.

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?

The description does not explicitly state when to use this tool versus alternatives. It implies the scope (display/sleep settings) but gives no exclusions or comparisons with other update tools. The confirmation behavior for open_to_public is a usage note, but there is no guidance on when not to use this tool.

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