Skip to main content
Glama

caelus-mcp

by io.github.heavyblotto

current_sky

The sky at a moment and place — not tied to any person. Use for "what's the sky/transits right now" or the chart of a non-birth event. Date defaults to now; lat/lon default to 0,0 (geocentric on the equator at the prime meridian), where houses and ASC/MC are nominal — pass a real location if houses matter. For a specific person's birth chart use natal_chart instead. Returns positions, houses, retrogrades, aspects.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
latNoLatitude, north positive; default 0 makes houses nominal
lonNoLongitude, EAST positive (Americas are negative); default 0 makes houses nominal
dateNoUTC ISO date-time (convert from local first); omit for now
gridNoCanonical grid (with output:'canonical'): arcsec (default), milliarcsec, centideg, dms ([deg,min,sec] triples), or accuracy (each body snapped to its measured validated accuracy — the most portable choice for cross-platform content addressing)arcsec
outputNo'float' (default) returns the usual floating-point payload. 'canonical' returns integers on a declared grid plus a sha256 digest: stable across machines/browsers/languages, hashable for caching and dedupe, precision-honest, with sign/house/aspects re-derived from the quantized values so displayed numbers and facts always agreefloat
zodiacNotropical (default) or sidereal:<ayanamsa>tropical
remaindersNoWith output:'canonical': also return the remainder set — the integer sub-quantum residues quantization discarded, keyed by leaf path and bound to the payload digest. 'auto' picks one grid finer than the base; or name the refinement grid (must be strictly finer). Residues telescope: composeRemainders(payload, remainders) rebuilds the finer-grid payload exactly. Time residues are integer microseconds, distance residues integer nano-AU
separationNoAspect separation: 'longitude' (default, the zodiacal aspect) or 'spatial' (true great-circle separation accounting for ecliptic latitude — differs for the Moon, Pluto, and bodies far off the ecliptic)longitude
house_systemNoHouse system (default placidus). Case- and spacing-insensitive; valid: placidus, whole_sign, equal, porphyry, koch, regiomontanus, campanus, alcabitius, morinus, meridian, polich_page, vehlow (aliases like "whole sign" also work).placidus

TDQS

A4.4/5.0
Behavior4/5

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

With no annotations, the description carries the full burden. It discloses defaults (date=now, lat/lon=0,0 geocentric), the consequence for houses/ASC/MC, and the non-personal scope. It stops short of discussing errors or rate limits, but those are not essential for this simple lookup-style tool.

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

Conciseness5/5

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

Four compact sentences front-load the purpose, then provide usage guidance and a pointer to the alternative tool. No filler or redundancy.

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?

Given 9 params (all documented in schema) and no output schema, the description covers the core use cases, critical defaults, and output summary. It leaves specialized mode parameters (grid, canonical output, remainders) to the schema, which is acceptable, though a brief mention of the canonical/digest option would be slightly more complete.

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 baseline is 3. The description adds practical context about location defaults making houses nominal, but does not systematically add meaning beyond the schema's per-parameter descriptions.

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 clearly names the resource ('the sky at a moment and place') and core outputs (positions, houses, retrogrades, aspects). It explicitly differentiates from sibling tool natal_chart, making the purpose unmistakable.

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 concrete when-to-use cases ('what's the sky/transits right now', chart of a non-birth event) and an explicit alternative ('For a specific person's birth chart use natal_chart instead'). Also warns about nominal houses and advises passing a real location when houses matter.

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

All caelus-mcp toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.9/5.0
Disambiguation5/5

Each tool has a highly specific and well-described purpose. Despite the large number, their functions are clearly distinct—e.g., natal_chart vs current_sky vs composite, or dasha vs firdaria vs profections vs releasing. The detailed descriptions prevent ambiguity.

Naming Consistency3/5

Names are consistently in snake_case but vary in style: some are noun phrases (natal_chart, cosmic_weather), some are verb-like (releasing, returns), and some are descriptive (aspect_patterns, find_aspect_dates). There is no strict verb_noun pattern, leading to moderate consistency.

Tool Count4/5

34 tools is high but appropriate for a comprehensive astrology API covering natal, transits, progressions, returns, synastry, time-lord techniques, sky events, and synthetic bodies. Each tool serves a specific niche, so the count feels justified rather than excessive.

Completeness5/5

The tool surface is extremely thorough, covering all major areas of astrology: chart generation, aspects, configurations, dignities, time-lord techniques (multiple systems), synastry, composite, progressions, returns, transits, sky events, rectification, electional, and synthetic bodies. No obvious gaps for the intended domain.

Resources