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 7): 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 observed

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, so the description adds real value: it discloses the period cap (max 7 days, default 7, shrinking to 1 with a satellite), the default separation window, and that results carry visibility assessments (above horizon, dark sky). It stops short of describing result ordering or precision limits.

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?

Front-loaded with the core concept and the object set before the satellite variation and the disambiguation note. Dense single sentence with heavy parentheticals, but every clause (object list, visibility, angular-vs-spatial caveat) carries information rather than filler.

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?

With nine parameters, no output schema, and only minimal annotations, the description does the needed work: it characterizes the return content qualitatively and explains the two operating modes. Completeness would be higher with an explicit note on how many conjunctions to expect or how visibility filtering affects the result set.

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 adds cross-parameter semantics the schema does not state: that supplying a satellite switches the period to one day of passes and that the pairing set is bounded to bright ecliptic stars. It does not expand on max_separation, time_zone, or lang 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?

Names a specific phenomenon (apparent close pairings seen from a place over a period), enumerates the objects involved (Moon, planets, and named ecliptic stars), and states what is returned (closest approach, where to look, visibility). It explicitly distinguishes itself from perigee_close_approach as angular sky separations rather than distances in space.

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?

Explicitly routes the agent away from this tool when true physical distance is wanted ("use perigee_close_approach"), and explains the satellite branch as an alternate mode covering one day of passes. It lacks any guidance relative to the obvious neighbors for sky viewing (perigee_sky, perigee_tonight, perigee_passes), leaving some selection ambiguity.

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