Skip to main content
Glama

The sky from a place

perigee_sky
Read-only

What is in the sky from a place at a date (default: now): day, twilight or night; the Sun with its next rise, set and twilights; the Moon with its phase, illuminated share, rise and set; each planet with its altitude, direction, brightness…

Instructions

What is in the sky from a place at a date (default: now): day, twilight or night; the Sun with its next rise, set and twilights; the Moon with its phase, illuminated share, rise and set; each planet with its altitude, direction, brightness (magnitude), constellation and whether it can be seen with the naked eye; and the bright named stars above the horizon. A snapshot at one moment; give the coordinates of the place (Perigee does no geocoding). For a ready summary of the coming night use perigee_tonight; for dated events over days or weeks, perigee_events.

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

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.4/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 is covered; the description adds that this is a single-moment snapshot rather than a time series and that no geocoding is performed server-side. With no output schema, the enumeration of returned bodies and attributes is valuable behavioral context. It stops short of stating error behavior or limits, so not a 5.

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 statement and the alternative-routing sentence are front-loaded and waste no words. The middle sentence is a long enumerated list, but since there is no output schema that content earns its place; it could be broken up for readability.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a read-only snapshot tool with six fully documented parameters and no output schema, the description covers what is returned, the time semantics, the input prerequisite, and the sibling alternatives. An agent has everything needed to call it correctly and to avoid calling it when perigee_tonight or perigee_events fits better.

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 latitude, longitude, date, lang, height_m and time_zone are already fully documented including ranges, enum and default. The description only reinforces that coordinates are mandatory and that the date defaults to now, adding little beyond the schema. Baseline 3 is appropriate.

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 question the tool answers ('What is in the sky from a place at a date') and enumerates the resources returned: Sun, Moon, planets with magnitude/constellation/naked-eye visibility, and bright named stars. It explicitly separates itself from perigee_tonight and perigee_events, so an agent can pick it 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 the selecting condition for two named alternatives: perigee_tonight for a ready summary of the coming night, perigee_events for dated events over days or weeks. It also states the precondition that coordinates must be supplied because Perigee does no geocoding, which prevents a predictable misuse.

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