Skip to main content
Glama

Close pairings in the sky

perigee_sky_conjunctions
Read-only

Apparent close pairings seen from a place over a period (default 7 days, at most 31): the Moon and the planets with each other and with the bright stars near the ecliptic (Regulus, Spica, Antares, Aldebaran, Pollux…), at their closest…

Instructions

Apparent close pairings seen from a place over a period (default 7 days, at most 31): the Moon and the planets with each other and with the bright stars near the ecliptic (Regulus, Spica, Antares, Aldebaran, Pollux…), at their closest, with where to look and whether the pair is visible (above the horizon, dark sky). With satellite (a NORAD number), that satellite passing near them during its passes over one day. Angles on the sky, not distances in space (use perigee_close_approach).

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "latitude": "<latitude>",
      "longitude": "<longitude>"
    },
    "name": "perigee_sky_conjunctions"
  }
}

Input Schema

NameRequiredDescriptionDefault
daysNoLength of the period in days (default 7; 1 with a satellite).
langNoLanguage of names and texts (default en).
startNoISO 8601 UTC instant, e.g. 2026-12-01T00:00:00Z (default: now).
height_mNoObserver height above sea level, m.
latitudeYesObserver latitude, degrees (north positive).
longitudeYesObserver longitude, degrees (east positive).
satelliteNoAn Earth satellite (NORAD number) to check against the Moon, planets and stars.
time_zoneNoIANA time zone for local times, e.g. "Europe/Paris".
max_separationNoWidest separation kept, degrees (default 5).

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 only declare readOnlyHint and openWorldHint; the description adds substantive context beyond them — the default and maximum period, the one-day behavior when a satellite is given, and that results report where to look and whether the pair clears the horizon in a dark sky. There is no output schema, and the description does sketch the result content, though it does not describe ordering, count limits, or how many pairs may be returned.

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?

A single front-loaded sentence leads with the phenomenon, then the object set, then the satellite variant, then the disambiguation — a logical order with no filler. It is dense and parenthetical, which slows parsing slightly, but every clause carries information.

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 nine-parameter ephemeris query with no output schema, the description covers the domain, the default window, the satellite variant, and the nature of the returned visibility information, which is what an agent needs to select and call it. Remaining gaps (result volume, local-time formatting via time_zone, effect of height_m) are modest given the fully documented schema.

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 coverage is 100%, so the baseline is 3, but the description goes further by explaining cross-parameter semantics the schema cannot: that the `satellite` value changes the effective period to one day of passes and that separations are angular on-sky measures. It does not explain the meaning of max_separation or how height_m affects visibility, leaving some room above baseline.

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 gives a specific verb-and-resource ('apparent close pairings seen from a place over a period') and enumerates the exact object set covered (Moon, planets, bright ecliptic stars), so an agent can distinguish it from general sky or distance tools at a glance. It also names the sibling it is not, perigee_close_approach, for real-space distances.

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

Usage Guidelines4/5

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

It states the operating window (default 7 days, at most 31) and the condition that changes behavior (supplying a satellite reduces the window to one day of passes), and it explicitly routes angular-vs-physical-distance questions to perigee_close_approach. It does not contrast with perigee_sky or perigee_tonight, so the when-not guidance is partial rather than exhaustive.

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