Skip to main content
Glama

Tonight from a place

perigee_tonight
Read-only

What there is to see tonight from a place (the coming night, or the current one): the night's start and end, the Moon (phase, illuminated share, rise and set), the planets visible to the naked eye, the visible passes of the ISS, Tiangong…

Instructions

What there is to see tonight from a place (the coming night, or the current one): the night's start and end, the Moon (phase, illuminated share, rise and set), the planets visible to the naked eye, the visible passes of the ISS, Tiangong and Hubble, the close pairings of the Moon and planets, and the sky's events of the night, with short highlights ready to read. Give the place's latitude and longitude and, for local times, its IANA time zone (Perigee does no geocoding). It combines perigee_sky, perigee_passes, perigee_sky_conjunctions and perigee_events for one night: use those for another moment, another satellite or a longer period.

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_tonight"
  }
}

Input Schema

NameRequiredDescriptionDefault
dateNoISO 8601 UTC instant, e.g. 2026-12-01T00:00:00Z (default: now).
langNoLanguage of names and texts (default en).
height_mNoObserver height above sea level, m.
latitudeYesObserver latitude, degrees (north positive).
longitudeYesObserver 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.5/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 a genuinely important constraint beyond them: 'Perigee does no geocoding,' so the caller must supply coordinates itself, plus the conditional that a time zone is needed for local times. It does not discuss response size, cost, or latency of an aggregate call, which is the one gap for a tool fanning out to four others.

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-loads the what, then the input requirements, then the sibling routing — the right order for an agent. The enumerated content list is long but each item earns its place by defining coverage; only slight trimming would be possible.

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 no output schema, the description carries the return-value burden, and it does so by listing the sections the response contains plus the note that highlights are 'ready to read.' It stops short of describing the response's shape or ordering, but an agent can predict what comes back well enough to choose this tool.

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 would be 3, but the description adds meaning the schema does not: latitude/longitude are mandatory because there is no geocoding, and time_zone affects whether times are local or UTC. That clarifies the practical consequence of each parameter rather than restating its type.

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 specific verb-less but concrete outcome — 'what there is to see tonight from a place' — and then enumerates the exact contents (night start/end, Moon phase and rise/set, naked-eye planets, ISS/Tiangong/Hubble passes, Moon-planet pairings, events, highlights). This distinguishes it clearly from the aggregate sibling tools it names.

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?

Explicitly scopes itself to one night ('the coming night, or the current one') and names the four components it combines (perigee_sky, perigee_passes, perigee_sky_conjunctions, perigee_events), then states the exclusion: use those instead for another moment, another satellite, or a longer period. Both when-to-use and when-not-to-use are present.

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