Skip to main content
Glama

Celestium: Cosmic Compass

celestium

Read-only

Celestium: Cosmic Compass — accurate astrology & divination for AI agents, with engine-authored interpretations attached (not LLM guesswork; real ephemeris, verified arcminute-accurate). Includes practice actions: check_in (sky + moment verdict + matched ritual), ritual (step-by-step moon-phase practices), tarot (auditable draws), review (temporal review of a period against your chart). Actions: cosmic_weather, chart, positions, moon, moment_quality, retrograde, voc, planetary_hours, sunrise, ritual, tarot, check_in, natal_reading, iching, mayan, numerology, true_sky, event_debrief, composite, davison, relocation, relocation_score, travel, transits, synastry, timing, progressions, electional, horary, returns, timeline, synthesis, perfections, midpoints, harmonic, antiscia, declination, sidereal, heliacal, review, bazi, year_ahead, correlate, common_threads. Free tier: cosmic_weather, chart, positions, moon, moment_quality, retrograde, voc, planetary_hours, sunrise, ritual, tarot, check_in, natal_reading, iching, mayan, numerology, true_sky, event_debrief. Celestium Pro unlocks depth + relationship charts (synastry/composite/davison), astrocartography (relocation/travel), advanced techniques, and review.

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": {
      "action": "<action>"
    },
    "name": "celestium"
  }
}

Input Schema

NameRequiredDescriptionDefault
dataNoBirth data + params. birth: {name, birth_date (YYYY-MM-DD), birth_time (HH:MM), birth_timezone (IANA), latitude, longitude, birth_location}. partner: same birth shape (synastry/composite/davison; also adds relationship activations to cosmic_weather/check_in). For place-based actions (relocation, relocation_score, planetary_hours, sunrise, heliacal, electional), top-level latitude/longitude = the TARGET location. Plus optional date, start, end, return_type (solar|lunar), city, planet, number (harmonic), orb (antiscia), system (sidereal: lahiri|raman|kp), activity (electional: marriage|business|travel|surgery|legal_matter|creative_work|investment|medical_treatment), ritual: type + max_minutes; tarot: count (1-3) + question; iching: question; check_in: mood, focus, intent, local_hour; review: period (week|month) or start+end; horary: question + house (1-12) + latitude/longitude; bazi: gender (male|female). render: true (natal_reading only) → also returns a viewable_url: a shareable, unlisted, auto-expiring, revocable web page of the chart+reading; render:{ttl_days:N} sets the expiry (default 90d), render:{burn:true} makes it view-once, render:{e2ee:true} encrypts it at rest (key only in the link #fragment; we store ciphertext and cannot read it). Nothing is stored unless you opt in with render; without it, calls are pure compute.
actionYesThe astrology/divination action to run.
identityNoCelestium agent token (tok_...) from https://celestium.me/dash; unlocks Pro. Plain emails no longer unlock Pro. Optional: omit for the free tier.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / identity / description
      Previous value: -"Caller email/identity (resolves entitlement tier; optional in free tier)."New value: +"Celestium agent token (tok_...) from https://celestium.me/dash; unlocks Pro. Plain emails no longer unlock Pro. Optional: omit for the free tier."
  2. Changed1 schema field changed
    • changedInput schema / properties / action / enum
      Previous value: -[
      -  "cosmic_weather",
      -  "chart",
      -  "positions",
      -  "moon",
      -  "moment_quality",
      -  "retrograde",
      -  "voc",
      -  "planetary_hours",
      -  "sunrise",
      -  "ritual",
      -  "tarot",
      -  "check_in",
      -  "natal_reading",
      -  "iching",
      -  "mayan",
      -  "numerology",
      -  "true_sky",
      -  "composite",
      -  "davison",
      -  "relocation",
      -  "relocation_score",
      -  "travel",
      -  "transits",
      -  "synastry",
      -  "timing",
      -  "progressions",
      -  "electional",
      -  "horary",
      -  "returns",
      -  "timeline",
      -  "synthesis",
      -  "perfections",
      -  "midpoints",
      -  "harmonic",
      -  "antiscia",
      -  "declination",
      -  "sidereal",
      -  "heliacal",
      -  "review",
      -  "bazi",
      -  "year_ahead",
      -  "correlate",
      -  "common_threads"
      -]New value: +[
      +  "cosmic_weather",
      +  "chart",
      +  "positions",
      +  "moon",
      +  "moment_quality",
      +  "retrograde",
      +  "voc",
      +  "planetary_hours",
      +  "sunrise",
      +  "ritual",
      +  "tarot",
      +  "check_in",
      +  "natal_reading",
      +  "iching",
      +  "mayan",
      +  "numerology",
      +  "true_sky",
      +  "event_debrief",
      +  "composite",
      +  "davison",
      +  "relocation",
      +  "relocation_score",
      +  "travel",
      +  "transits",
      +  "synastry",
      +  "timing",
      +  "progressions",
      +  "electional",
      +  "horary",
      +  "returns",
      +  "timeline",
      +  "synthesis",
      +  "perfections",
      +  "midpoints",
      +  "harmonic",
      +  "antiscia",
      +  "declination",
      +  "sidereal",
      +  "heliacal",
      +  "review",
      +  "bazi",
      +  "year_ahead",
      +  "correlate",
      +  "common_threads"
      +]
  3. Changed1 schema field changed
    • changedInput schema / properties / action / enum
      Previous value: -[
      -  "cosmic_weather",
      -  "chart",
      -  "positions",
      -  "moon",
      -  "moment_quality",
      -  "retrograde",
      -  "voc",
      -  "planetary_hours",
      -  "sunrise",
      -  "ritual",
      -  "tarot",
      -  "check_in",
      -  "natal_reading",
      -  "iching",
      -  "mayan",
      -  "numerology",
      -  "composite",
      -  "davison",
      -  "relocation",
      -  "relocation_score",
      -  "travel",
      -  "transits",
      -  "synastry",
      -  "timing",
      -  "progressions",
      -  "electional",
      -  "horary",
      -  "returns",
      -  "timeline",
      -  "synthesis",
      -  "perfections",
      -  "midpoints",
      -  "harmonic",
      -  "antiscia",
      -  "declination",
      -  "sidereal",
      -  "heliacal",
      -  "review",
      -  "bazi",
      -  "year_ahead",
      -  "correlate"
      -]New value: +[
      +  "cosmic_weather",
      +  "chart",
      +  "positions",
      +  "moon",
      +  "moment_quality",
      +  "retrograde",
      +  "voc",
      +  "planetary_hours",
      +  "sunrise",
      +  "ritual",
      +  "tarot",
      +  "check_in",
      +  "natal_reading",
      +  "iching",
      +  "mayan",
      +  "numerology",
      +  "true_sky",
      +  "composite",
      +  "davison",
      +  "relocation",
      +  "relocation_score",
      +  "travel",
      +  "transits",
      +  "synastry",
      +  "timing",
      +  "progressions",
      +  "electional",
      +  "horary",
      +  "returns",
      +  "timeline",
      +  "synthesis",
      +  "perfections",
      +  "midpoints",
      +  "harmonic",
      +  "antiscia",
      +  "declination",
      +  "sidereal",
      +  "heliacal",
      +  "review",
      +  "bazi",
      +  "year_ahead",
      +  "correlate",
      +  "common_threads"
      +]
  4. Changed1 schema field changed
    • changedInput schema / properties / data / description
      Previous value: -"Birth data + params. birth: {name, birth_date (YYYY-MM-DD), birth_time (HH:MM), birth_timezone (IANA), latitude, longitude, birth_location}. partner: same birth shape (synastry/composite/davison; also adds relationship activations to cosmic_weather/check_in). For place-based actions (relocation, relocation_score, planetary_hours, sunrise, heliacal, electional), top-level latitude/longitude = the TARGET location. Plus optional date, start, end, return_type (solar|lunar), city, planet, number (harmonic), orb (antiscia), system (sidereal: lahiri|raman|kp), activity (electional: marriage|business|travel|surgery|legal_matter|creative_work|investment|medical_treatment), ritual: type + max_minutes; tarot: count (1-3) + question; iching: question; check_in: mood, focus, intent, local_hour; review: period (week|month) or start+end; horary: question + house (1-12) + latitude/longitude; bazi: gender (male|female). render: true (natal_reading only) → also returns a viewable_url: a shareable, unlisted, revocable web page of the chart+reading; pass render:{ttl_days:N} to auto-expire it. Nothing is stored unless you opt in with render; without it, calls are pure compute."New value: +"Birth data + params. birth: {name, birth_date (YYYY-MM-DD), birth_time (HH:MM), birth_timezone (IANA), latitude, longitude, birth_location}. partner: same birth shape (synastry/composite/davison; also adds relationship activations to cosmic_weather/check_in). For place-based actions (relocation, relocation_score, planetary_hours, sunrise, heliacal, electional), top-level latitude/longitude = the TARGET location. Plus optional date, start, end, return_type (solar|lunar), city, planet, number (harmonic), orb (antiscia), system (sidereal: lahiri|raman|kp), activity (electional: marriage|business|travel|surgery|legal_matter|creative_work|investment|medical_treatment), ritual: type + max_minutes; tarot: count (1-3) + question; iching: question; check_in: mood, focus, intent, local_hour; review: period (week|month) or start+end; horary: question + house (1-12) + latitude/longitude; bazi: gender (male|female). render: true (natal_reading only) → also returns a viewable_url: a shareable, unlisted, auto-expiring, revocable web page of the chart+reading; render:{ttl_days:N} sets the expiry (default 90d), render:{burn:true} makes it view-once, render:{e2ee:true} encrypts it at rest (key only in the link #fragment; we store ciphertext and cannot read it). Nothing is stored unless you opt in with render; without it, calls are pure compute."
  5. First observed

TDQS

B3/5.0
Behavior2/5

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

The description does add real context beyond annotations: interpretation provenance, ephemeris accuracy, and an explicit storage model ('Nothing is stored unless you opt in with render'), plus ttl_days/burn/e2ee render semantics. However, that render path creates a persistent, shareable, revocable web page and stores ciphertext at rest, which is a write side effect that conflicts with the declared readOnlyHint=true. An agent trusting the annotation alone would not expect any persistence.

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

Conciseness2/5

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

It is front-loaded, but the opening is promotional ('Cosmic Compass', 'not LLM guesswork', 'verified arcminute-accurate') rather than operational. The 44-action enumeration and the 18-item free-tier list substantially duplicate the action enum already present in the schema, inflating length without adding dispatch semantics.

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

Completeness3/5

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

For a mega-tool with 44 actions and no output schema, the description plus the very rich nested data schema cover inputs and the storage/rendering model adequately. What is missing is per-action behavior: return shape, cost/latency, and what most of the advanced technique actions produce. An agent can invoke free-tier actions confidently but must guess at the depth actions.

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% and the nested data object already documents birth/partner shapes, target latitude/longitude for place-based actions, and per-action options like ritual, tarot, horary, and bazi. The description text itself adds nothing to parameter meaning beyond the schema, so the baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The opening states a specific resource and scope: an astrology/divination engine with ephemeris-backed, engine-authored interpretations rather than LLM guesses. It also separates free-tier and Pro capabilities, which tells an agent what class of work the tool covers. It loses a point because the 44 action names are only labels — an agent still can't tell from the description what 'perfections', 'synthesis', or 'heliacal' actually do.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is genuine routing guidance in the free-tier vs Pro split (synastry/composite/davison, astrocartography, and review are paywalled), which helps an agent anticipate auth requirements. But there is no guidance on when to pick which of the 44 actions, and no statement of when not to use the tool or what to do instead. Usage is implied by action names rather than explained.

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