Skip to main content
Glama

Sky calendar

get_upcoming_events
Read-only

Lists changes in the sky over a window of up to 92 days: planets changing sign, planets turning retrograde or direct, and new and full Moons. With no input it covers the next seven days. It fits a question about what is coming up in the sky over the next days or weeks. It does not list eclipses or every aspect. It lists dates and makes no prediction. A request to set a reminder or an alert, or to schedule anything, is not a request for this tool, not even to look the date up first: Zodiacs sets no reminders and schedules nothing. Nor is a stock or lottery pick, an investment call, a bet, an election or health forecast, or a guarantee. The window is at most 92 days, within 1800 to 2199. Without a time zone its times are in UTC. Its times for a slow planet's sign change come from the engine and can differ from NASA JPL Horizons by hours: for Neptune entering Aries on 26 January 2026 it gives 14:32 UTC, where Horizons gives 17:35 UTC.

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": "get_upcoming_events"
  }
}

Input Schema

NameRequiredDescriptionDefault
toNoA moment as an ISO 8601 time with Z or an offset, such as 2026-10-08T09:00:00-06:00 (years 1800–2199).
fromNoA moment as an ISO 8601 time with Z or an offset, such as 2026-10-08T09:00:00-06:00 (years 1800–2199).
zoneNoThe person's time zone, such as America/Mexico_City or America/New_York. Without it, times are in UTC.
kindsNo
bodiesNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • changedInput schema / properties / from / description
      Previous value: -"A moment as an ISO 8601 time with Z or an offset, such as 2026-10-08T09:00:00+07:00 (years 1800–2199)."New value: +"A moment as an ISO 8601 time with Z or an offset, such as 2026-10-08T09:00:00-06:00 (years 1800–2199)."
    • changedInput schema / properties / to / description
      Previous value: -"A moment as an ISO 8601 time with Z or an offset, such as 2026-10-08T09:00:00+07:00 (years 1800–2199)."New value: +"A moment as an ISO 8601 time with Z or an offset, such as 2026-10-08T09:00:00-06:00 (years 1800–2199)."
    • changedInput schema / properties / zone / description
      Previous value: -"The person's time zone, such as Asia/Bangkok or America/New_York. Without it, times are in UTC."New value: +"The person's time zone, such as America/Mexico_City or America/New_York. Without it, times are in UTC."
  2. First observed

TDQS

A4.3/5.0
Behavior5/5

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

Annotations already declare readOnly=true, openWorld=false, destructive=false, so the safety profile is covered; the description goes further with defaults (no input = next seven days), the 92-day ceiling, UTC fallback for times, the 1800–2199 range, and a concrete accuracy caveat against JPL Horizons for slow-planet ingresses. That precision/uncertainty disclosure is behavior an agent could not get from the schema or annotations, and 'it lists dates and makes no prediction' sets expectations about the return.

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

Conciseness3/5

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

The opening is well front-loaded: purpose, contents, default window, and scope of use all land in the first three sentences. The remainder sprawls, however, and the disclaimer chain (stock or lottery pick, investment call, a bet, an election, a health forecast, a guarantee) is redundant once 'makes no prediction' has been stated, while the Neptune/Horizons example consumes a long sentence. Trimming the negative list would tighten it without losing routing value.

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 zero-required-parameter, read-only listing tool with an output schema (so return shape need not be described), the definition covers defaults, bounds, time-zone handling, exclusions, and mis-routing. The one real gap is interaction between the kinds and bodies filters — whether omitting them returns everything, and what subset of bodies is used by default.

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

Parameters4/5

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

With schema coverage at 60%, the description compensates: it establishes that all inputs are optional and defaulted, defines the window semantics and its 92-day cap, and specifies the UTC fallback for the zone parameter. It also implicitly maps the undocumented enum parameters to phenomena (sign change = ingress, retrograde/direct = station, new/full Moon = lunation), which adds real meaning. It does not clarify how kinds and bodies filter results or what the default body set is.

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 and resource and enumerates contents precisely: planets changing sign, stations retrograde/direct, and new and full Moons over a window of up to 92 days. It also states exclusions (no eclipses, no aspects). It loses a point only because a sibling is literally titled 'Sky calendar' (get_sky_calendar) and the description never says how this listing differs from that one.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

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

It gives an explicit positive trigger ('a question about what is coming up in the sky over the next days or weeks'), explicit exclusions (eclipses, every aspect), and explicit mis-routing guards: reminder/alert/scheduling requests are not requests for this tool, 'not even to look the date up first.' It also anticipates adjacent-but-wrong intents (picks, bets, forecasts, guarantees). Nothing is left to inference.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.