Skip to main content
Glama
Sign In
skylight-mcp

skylight-mcp

by chrischall
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

skylight_get_frame

Read-only

Get a Skylight frame and its settings by optional frame ID; if omitted, it uses the resolved frame.

Instructions

Get one Skylight frame and its settings.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "skylight_get_frame"
  }
}

Input Schema

NameRequiredDescriptionDefault
frameIdNoFrame id; defaults to the resolved frame.

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. First observedv0.4.6

TDQS

B3.2/5.0
Behavior3/5

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

The annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds that the return includes the frame's settings, which is useful, but says nothing about auth requirements, behavior when the frame cannot be resolved, or error conditions. A 3 is appropriate given the annotations carry most of the burden.

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?

A single front-loaded sentence with no waste. It is arguably too terse for a tool description, but nothing is redundant or poorly ordered.

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 simple read tool with no required parameters, one well-documented parameter, and no output schema, the description covers what is fetched and that settings are included. Minor gaps remain on what 'settings' comprises and failure behavior when no frame is resolved.

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 description coverage is 100% and the single frameId parameter already documents that it defaults to the resolved frame. The description adds no format, id-shape, or lookup guidance beyond the schema, so the baseline 3 applies.

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 names a specific verb ('Get') and resource ('one Skylight frame and its settings'), and the singular 'one frame' implicitly contrasts with the sibling skylight_list_frames. It does not, however, explicitly differentiate itself from update_frame, rename_frame, or list_frames, so it stops 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 Guidelines2/5

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

There is no statement of when to call this versus skylight_list_frames (to enumerate frames) or the update/rename variants (to mutate one). The only usage hint is implicit in the word 'one'. No prerequisites or exclusions are given.

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