Skip to main content
Glama

caelus-mcp

by io.github.heavyblotto

returns

Solar or lunar return: the instant(s) a body returns to its natal longitude within a window, plus the full return chart for the first one. The Sun returns about yearly (the solar-return chart for the year), the Moon about monthly. Return chart is cast for the return moment at return_lat/return_lon (defaults to the birthplace; pass the current/relocated place for a relocated return).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
latYesLatitude, north positive
lonYesLongitude, EAST positive (Americas are negative)
bodyYessun for the solar return, moon for the lunar return
dateYesUTC date-time, ISO 8601, e.g. 1990-06-10T14:30:00Z. Convert local birth time to UTC first.
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
return_latNoLatitude for the return chart; defaults to the birth latitude
return_lonNoLongitude (EAST positive) for the return chart; defaults to the birth longitude
search_endYesUTC ISO end of the window; range <= 2 years
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
search_startYesUTC ISO start of the window to search for returns

TDQS

A4.4/5.0
Behavior4/5

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

No annotations are provided, so the description carries the full burden. It discloses key behaviors: it returns all instants but only the full chart for the first one, and it defaults the return chart location to birthplace with an override option. This adds meaningful context beyond just 'compute returns.'

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?

The description is three concise sentences, front-loaded with the core purpose, and each sentence adds essential information. No filler or repetition of schema details.

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 the high parameter count and no output schema, the description covers the essential behavior: what a return is, how often it happens, and how location is determined. It does not detail output format, but for a calculation tool this is sufficient for selection and invocation.

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 description coverage is 100%, so baseline is 3. The description enhances meaning for parameters: it explains the body parameter's effect (Sun yearly, Moon monthly) and the return_lat/return_lon default behavior (defaults to birthplace, override for relocated return), which adds value beyond the structured 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 states the tool computes solar or lunar returns: 'the instant(s) a body returns to its natal longitude within a window, plus the full return chart for the first one.' It distinguishes itself from other astrological tools by specifying the return concept and body types.

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?

It provides clear context on when returns occur ('The Sun returns about yearly... the Moon about monthly') and how to customize the return chart location ('pass the current/relocated place for a relocated return'). However, it does not explicitly name alternatives or state when not to use this tool.

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