Skip to main content
Glama
chrischall

skylight-mcp

by chrischall
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

skylight_generate_activity_ideas

Generate AI activity or event ideas for a location and time range, then create draft events asynchronously for your family calendar.

Instructions

Generate AI activity/event ideas for a location and time range (creates draft events — async).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
budgetNoe.g. "$50".
frameIdNo
category_idsYesFamily-member category ids the activities are for.
activity_kindNoe.g. "local_event".
physical_locationYesLocation, e.g. "Charlotte, NC, USA".
datetime_range_endYesISO datetime.
datetime_range_startYesISO datetime.

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. Changed2 schema fields changedv0.7.1
    • removedInput schema / properties / category_ids / items / anyOf
      Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "number"
-  }
-]
    • addedInput schema / properties / category_ids / items / type
      Added value: +[
+  "string",
+  "number"
+]
  3. First observedv0.4.6

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare a non-readonly, open-world, non-destructive operation, so the safety profile is covered. The description adds genuinely useful context beyond that: it discloses that output is draft events (not committed events) and that the operation is asynchronous, which materially changes how an agent should follow up.

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 well-formed sentence that front-loads the core action and appends the crucial async/draft caveat. Every clause earns its place with no filler.

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 7-parameter write tool with no output schema, the description conveys the essential behavioral facts (drafts, async) that an agent needs before invoking. It is slightly incomplete in not indicating how the resulting drafts are surfaced or approved, which matters given sibling draft/approval tools, but the coverage is otherwise solid.

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 86%, so the schema already documents parameters like physical_location, datetime_range_start/end, category_ids, budget, and activity_kind. The description only restates 'location and time range' and adds no format, constraint, or default detail beyond the schema.

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 (generate) and resource (activity/event ideas) scoped to a location and time range, and notes it creates draft events asynchronously. It is clearly distinguishable from create_event (which makes a single event), but it does not explicitly name or contrast with its nearest sibling, generate_meal_plan, or the auto-creation draft tools.

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?

The description describes the input scope but gives no when-to-use guidance: nothing tells the agent when to prefer this over skylight_create_event or skylight_generate_meal_plan, nor when not to use it. Usage is only implied by the resource name.

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