Skip to main content
Glama

Astronomical and mission events

perigee_events
Read-only

Events over a period (default: the next 30 days, at most 366): Moon phases (super and micro full Moons), lunar perigee and apogee, lunar and solar eclipses (contact times; with a place: how they look from there, with the duration of…

Instructions

Events over a period (default: the next 30 days, at most 366): Moon phases (super and micro full Moons), lunar perigee and apogee, lunar and solar eclipses (contact times; with a place: how they look from there, with the duration of totality or annularity and the altitude of the Sun or the Moon), equinoxes and solstices, the Earth's perihelion and aphelion, planet oppositions, conjunctions and greatest elongations, and the next key events of the missions (flybys, arrivals, launches) from Perigee's catalogue. Worldwide dates, not what is up at a given moment (use perigee_sky).

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

Input Schema

NameRequiredDescriptionDefault
daysNoLength of the period in days (default 30).
langNoLanguage of names and texts (default en).
kindsNoKinds of events to include (default: all).
startNoISO 8601 UTC instant, e.g. 2026-12-01T00:00:00Z (default: now).
latitudeNoObserver latitude, degrees (north positive).
longitudeNoObserver longitude, degrees (east positive).
time_zoneNoIANA time zone for local times, e.g. "Europe/Paris".

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.10.0

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety and locality are covered; the description adds real context beyond that, including the default window (next 30 days), the hard cap (at most 366), and the extra payload for eclipses (contact times, duration of totality or annularity, Sun/Moon altitude). It also discloses provenance ('from Perigee's catalogue'). It does not describe result ordering or shape, which keeps it below a 5 given there is no output schema.

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?

The scope and the period default are front-loaded, and the sibling exclusion lands at the end as a routing cue. The event enumeration is a single long, clause-heavy sentence that is dense but every item earns its place by telling the agent what kinds values map to.

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 seven-parameter, zero-required, read-only catalogue query with no output schema, the description covers the period semantics, the place-based variant, the event taxonomy and the routing exclusion. The main remaining gap is the shape of a returned event record (fields, ordering), which the description leaves implicit.

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%, so all seven parameters are already documented and the baseline is 3. The description does add meaning for latitude/longitude by explaining that a place yields a local view of eclipses with totality duration and Sun/Moon altitude, which is more than the schema's bare 'Observer latitude, degrees', but it says nothing extra about days, start, kinds, lang, or time_zone beyond what the schema states.

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?

The description states a specific resource (astronomical and mission events over a period) and enumerates the concrete event families returned: Moon phases including super/micro full Moons, perigee/apogee, eclipses with contact times, equinoxes and solstices, perihelion/aphelion, planet oppositions/conjunctions/elongations, and mission flybys/arrivals/launches. It also draws the boundary against the nearest sibling: 'Worldwide dates, not what is up at a given moment (use perigee_sky).'

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 names the alternative explicitly (perigee_sky) and the condition that selects it ('what is up at a given moment'), which is exactly the discriminator an agent needs. It also signals the optional place-based mode ('with a place: how they look from there'), telling the agent that supplying latitude/longitude changes the output rather than being required.

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