Skip to main content
Glama
chrischall

skylight-mcp

by chrischall
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

skylight_copy_messages_to_frames

Copy selected message or photo IDs from one Skylight frame to multiple destination frames, using frame IDs from skylight_list_frames to manage content across devices.

Instructions

Copy messages/photos from this frame to other frames on the account (inferred from the app bundle, not live-verified).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
frameIdNo
message_idsYesMessage/photo ids to copy.
new_frame_idsYesDestination frame ids (see skylight_list_frames).

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. Changed4 schema fields changedv0.7.1
    • removedInput schema / properties / message_ids / items / anyOf
      Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "number"
-  }
-]
    • addedInput schema / properties / message_ids / items / type
      Added value: +[
+  "string",
+  "number"
+]
    • removedInput schema / properties / new_frame_ids / items / anyOf
      Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "number"
-  }
-]
    • addedInput schema / properties / new_frame_ids / items / type
      Added value: +[
+  "string",
+  "number"
+]
  3. Addedv0.5.0

TDQS

A3.6/5.0
Behavior3/5

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

The description adds a useful caveat—'inferred from the app bundle, not live-verified'—beyond the annotations. However, it does not disclose potential side effects, failure modes, or behavior when frameId is omitted, which matters since annotations only indicate readOnlyHint=false and destructiveHint=false.

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

Conciseness5/5

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

A single, direct sentence that is front-loaded with the core action and resource. There is no redundant or filler content.

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 copy operation with a small parameter set, the description covers the essential action, source, destination, and a key caveat. It lacks some guidance around optional frameId and return behavior, but not enough to make the tool unusable for an agent.

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

Parameters3/5

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

Schema coverage is 67%, and the description vaguely aligns 'this frame' with frameId and 'other frames' with new_frame_ids, but it adds no deeper meaning about parameter formats, constraints, or relationships beyond what the schema already states.

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 names a specific verb ('Copy'), a concrete resource ('messages/photos'), and the source/destination relationship ('from this frame to other frames on the account'). This clearly distinguishes it from siblings like skylight_delete_messages or skylight_add_to_album.

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 explicit guidance on when to use this tool versus alternatives like skylight_add_to_album or skylight_upload_photo. The operation is implied, but there are no conditions, exclusions, or alternative routing.

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