Skip to main content
Glama
Sign In
Open Ephemeris

Open Ephemeris

by openephemeris
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Moment Quality Analysis

electional_moment_analysis
Read-onlyIdempotent

Evaluates a date or the current moment astrologically, returning planetary positions, aspects, lunar phase, sect, void-of-course status, and an electional score from 0 to 100.

Instructions

Use this when the user asks 'is today a good day to …', 'what's the sky like today', 'what's the astrological weather', 'how is this date astrologically' — or has no birth data (it works with no arguments). Returns planet positions, aspects, void-of-course status, lunar phase, day ruler, sect and an overall electional score (0-100) for one moment.

CREDIT COST: 5 credits per call.

Input Schema

NameRequiredDescriptionDefault
dateNoISO 8601; must include Z/offset. Default now.
formatNoOutput format.
latitudeNoLatitude, decimal degrees (+N). Optional; without coordinates sect defaults to diurnal.
longitudeNoLongitude, decimal degrees (+E). Pair with latitude.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv4.29.0
    • changedInput schema / properties / date / description
      Previous value: -"ISO 8601 datetime to analyze, with a zone (e.g., '2026-03-21T12:00:00Z' or '2026-03-21T08:00:00-04:00'). Defaults to now."New value: +"ISO 8601; must include Z/offset. Default now."
    • changedInput schema / properties / latitude / description
      Previous value: -"Latitude of location in decimal degrees (positive = North). Optional; without latitude and longitude, sect falls back to diurnal and a night moment is scored with the DAY triplicity rulers."New value: +"Latitude, decimal degrees (+N). Optional; without coordinates sect defaults to diurnal."
    • changedInput schema / properties / longitude / description
      Previous value: -"Longitude of location in decimal degrees (positive = East). Needed alongside latitude — day/night is a local fact that neither coordinate settles alone."New value: +"Longitude, decimal degrees (+E). Pair with latitude."
  2. Changed2 schema fields changedv4.24.2
    • addedInput schema / properties / latitude
      Added value: +{
+  "description": "Latitude of location in decimal degrees (positive = North). Optional; without latitude and longitude, sect falls back to diurnal and a night moment is scored with the DAY triplicity rulers.",
+  "type": "number"
+}
    • addedInput schema / properties / longitude
      Added value: +{
+  "description": "Longitude of location in decimal degrees (positive = East). Needed alongside latitude — day/night is a local fact that neither coordinate settles alone.",
+  "type": "number"
+}
  3. Changed1 schema field changedv4.8.0
    • changedInput schema / properties / date / description
      Previous value: -"ISO 8601 datetime to analyze (e.g., '2026-03-21T12:00:00'). Defaults to now."New value: +"ISO 8601 datetime to analyze, with a zone (e.g., '2026-03-21T12:00:00Z' or '2026-03-21T08:00:00-04:00'). Defaults to now."
  4. First observedv0.1.0

TDQS

A4/5.0
Behavior4/5

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

Annotations already establish that this is a read-only, idempotent, non-destructive operation. The description adds useful behavioral context by listing the returned data bundle and explicitly noting the 5-credit cost per call.

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 front-loaded with the user intents that should trigger it, followed by the return contents and cost. Every sentence carries useful selection or invocation information, with no wasted text.

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?

For a no-required-parameter analysis tool without an output schema, the description does enough by naming the returned fields and calling out the credit cost. It could be stronger if it briefly clarified how broadly the electional score should be interpreted or when a more targeted ephemeris tool is preferable.

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 date, format, latitude, and longitude are already well documented in the schema. The description adds only that the tool works with no arguments; it does not add further parameter meaning beyond the schema.

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 description clearly states that this tool analyzes the astrological quality of a single moment and returns an electional score plus supporting sky data. It distinguishes itself from natal-chart tools by emphasizing that no birth data is needed, but it does not explicitly differentiate itself from nearby ephemeris or moon-phase siblings.

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 gives clear example query patterns such as 'is today a good day to …' and 'what's the astrological weather', and notes that it works with no arguments. It does not say when to prefer a narrower sibling like moon-phase or aspect-check tools instead.

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

Deploy Server

Other Tools