Skip to main content
Glama
Sign In
skylight-mcp

skylight-mcp

by chrischall
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

skylight_set_reminder_profile

Set the global reminder cadence for Skylight Calendar to control how often reminders are nudged, using weeks between each reminder.

Instructions

Set the global reminder cadence (how often Skylight nudges about reminders).

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "interval_weeks": "<interval_weeks>"
    },
    "name": "skylight_set_reminder_profile"
  }
}

Input Schema

NameRequiredDescriptionDefault
interval_weeksYesHow many weeks between reminder nudges.

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.3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false and openWorldHint=true, so the safety profile is covered. The description adds the meaningful scoping fact that the change is 'global' rather than per-device or per-event, but says nothing about reversibility, permission requirements, or whether the setting persists across devices.

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 front-loaded sentence with a clarifying parenthetical and zero filler. Nothing could be removed without losing meaning.

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 one-parameter write tool with annotations covering the safety profile, the description is close to sufficient, but it leaves open what 'global' scopes over (household, account, all devices) and how it interacts with the event-notification and household-config tools. Not misleading, but thinner than a mutation tool of this reach warrants.

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 interval_weeks description ('How many weeks between reminder nudges') already conveys the unit and meaning. The description's phrase 'how often Skylight nudges about reminders' largely restates that, adding no new syntax or bounds information. 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?

States a specific verb (set) and resource (global reminder cadence), and the parenthetical gloss clarifies what a 'reminder profile' actually controls. It does not, however, distinguish itself from siblings like skylight_update_event_notification_settings or skylight_update_profile, so an agent must infer the boundary.

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 when-to-use guidance, no statement of prerequisites, and no mention of the adjacent tools that also touch notification/reminder behavior. The word 'global' hints at scope but the description never tells the agent when this is the right call versus those alternatives.

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