Skip to main content
Glama

The sky now

sky_now
Read-onlyIdempotent

The sky right now, or at any date and time from 1901 to mid-2100, in depth, from NASA JPL DE440. For every planet, the Sun, Moon, North Node and Lilith: sign and degree, ecliptic longitude and latitude, right ascension and declination (with out-of-bounds), distance, speed, retrograde status and its dates, when it entered its sign and when it leaves, and for planets their elongation from the Sun, phase and whether they are in the morning or evening sky. The Moon's phase, age, distance, next sign change, void-of-course window and next aspects, perigee and apogee; the aspects between the planets now (applying or separating); and a dated list of what comes in the next 30 days (full and new moons with their names, sign changes, retrograde stations, exact aspects). Answers "is Mercury retrograde?" and "what is the Moon in today?". Add a place to get the rising sign and midheaven there, each planet's house, and which planets are above the horizon (altitude and compass direction).

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

Input Schema

NameRequiredDescriptionDefault
dateNoOptional date, YYYY-MM-DD. Default: now.
timeNoOptional 24-hour HH:mm: local time at the place if one is given, otherwise UTC. Default: now (or noon on a given date).
placeNoOptional town or city, with country, for the rising sign, houses and what is above the horizon there.
latitudeNoOptional. Latitude of the place, if already known; skips the place search.
longitudeNoOptional. Longitude of the place, if already known.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changed
    • changedInput schema / properties / date / description
      Previous value: -"Optional date, YYYY-MM-DD (noon UTC). Default: right now."New value: +"Optional date, YYYY-MM-DD. Default: now."
    • addedInput schema / properties / latitude
      Added value: +{
      +  "description": "Optional. Latitude of the place, if already known; skips the place search.",
      +  "type": "number"
      +}
    • addedInput schema / properties / longitude
      Added value: +{
      +  "description": "Optional. Longitude of the place, if already known.",
      +  "type": "number"
      +}
    • addedInput schema / properties / place
      Added value: +{
      +  "description": "Optional town or city, with country, for the rising sign, houses and what is above the horizon there.",
      +  "maxLength": 200,
      +  "type": "string"
      +}
    • addedInput schema / properties / time
      Added value: +{
      +  "description": "Optional 24-hour HH:mm: local time at the place if one is given, otherwise UTC. Default: now (or noon on a given date).",
      +  "type": "string"
      +}
  2. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already carry the safety profile (readOnly, idempotent, non-destructive, openWorld), and the description adds genuinely useful context beyond them: the data source (JPL DE440), the hard date bounds, and the fact that supplying a place triggers location-dependent computation. It stops short of disclosing what happens on an unresolvable place name or any latency/rate behavior.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Purpose is front-loaded in the first clause, but the remainder is a single run-on enumeration of every returned field. Because no output schema exists the enumeration earns its place, yet it would read far better as a structured list rather than one 120-word sentence.

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?

With no output schema, the description carries the full burden of describing returns, and it does so exhaustively — planetary positions, aspects, Moon details, forward 30-day calendar, and the place-dependent extras. An agent knows what it will get back and what each input unlocks.

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 baseline is 3, but the description adds real meaning: the place parameter is what unlocks rising sign, house cusps and above-horizon altitudes, which is not obvious from the schema's wording alone. Latitude/longitude shortcutting the place search is also hinted at, though only the schema spells out the local-vs-UTC time rule.

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 precisely what it returns (full current-sky ephemeris snapshot) and its scope: now or any date from 1901 to mid-2100, sourced from NASA JPL DE440. The 'right now' framing implicitly separates it from the historical/computed chart siblings, and the enumerated bodies and fields make the resource unmistakable.

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?

Gives concrete triggering questions ('is Mercury retrograde?', 'what is the Moon in today?') and explains the add-a-place path for rising sign, houses and horizon data. It never names birth_chart or famous_chart as alternatives or states when-not to use it, so routing against siblings is left to inference.

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