Skip to main content
Glama

Astronomical and mission events

perigee_events
Read-only

Events over a period (default: the next 30 days, at most 31): 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 observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already cover safety (readOnlyHint=true, openWorldHint=false), so the description's job is added context, and it delivers: it discloses that supplying a place changes the response to local appearance with contact times, totality/annularity duration, and Sun/Moon altitude, versus worldwide dates otherwise. It stops short of describing result shape, event counts, or ordering, and there is no output schema to lean on.

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 sibling exclusion are front-loaded, and every clause names concrete event types rather than filler. It is a single dense run-on sentence-list, though, so the exclusion and the period defaults would scan faster if separated from the enumeration.

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, all-optional read tool with no output schema, the description covers what is returned (which event kinds), how the period defaults and caps, and how location changes results. The remaining gap is that nothing describes the response structure or ordering, which matters more given there is no output schema to document it.

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?

Schema description coverage is 100%, so a 3 is the baseline, but the description adds real meaning beyond the schema: it explains that latitude/longitude are not mere filters but switch the tool into a location-specific mode, and it restates the days default/ceiling as a hard bound. It does not clarify the semantics of lang, kinds, or time_zone beyond what the schema already says.

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 precise verb and resource ('Events over a period') and then enumerates the exact event families: Moon phases, perigee/apogee, eclipses, equinoxes/solstices, perihelion/aphelion, oppositions, conjunctions, elongations, mission events. It explicitly carves out scope against a named sibling ('not what is up at a given moment (use perigee_sky)'), so an agent can route without opening a schema.

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?

Gives an explicit when-to-use boundary ('Worldwide dates, not what is up at a given moment') and names the alternative tool that covers the excluded case. It also states operating bounds up front (default 30 days, at most 31), which prevents an invalid call before any schema read.

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.

Resources