Skip to main content
Glama
chrischall

skylight-mcp

by chrischall
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

skylight_generate_activity_ideas

Generate AI activity ideas for a specific location and time range. Provide dates and category IDs to receive draft events asynchronously.

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.9/5.0
Behavior4/5

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

Annotations only state readOnlyHint=false and destructiveHint=false; the description adds that the tool 'creates draft events' and is 'async', which clarifies that nothing is immediately committed and that results may need additional steps. This is meaningful behavioral context beyond the simple write/destructive flags, though it doesn't explain what happens after generation.

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?

One concise sentence with a clarifying parenthetical; it front-loads the core action and resource. No filler.

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?

The tool is async and creates drafts, but the description doesn't say what the response contains or how to retrieve the generated ideas (e.g., via list_auto_creation_drafts or get_auto_creation_intent). Given no output schema, the missing follow-up guidance leaves an agent guessing at the next step.

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 the parameters. The description only loosely maps to physical_location and datetime_range_start/end ('location and time range') without adding syntax or format details, so it adds little beyond the schema.

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?

States a specific verb ('Generate') and resource ('AI activity/event ideas for a location and time range'), and distinguishes itself from direct event creation by noting it 'creates draft events — async'. This clearly differentiates it from siblings like skylight_create_event and skylight_generate_meal_plan.

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 implies use when the user wants activity ideas for a place and time, but it gives no explicit when-not-to-use or alternatives. It does not name sibling tools such as skylight_create_event or skylight_list_events, leaving the agent to infer boundaries.

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