Skip to main content
Glama
openephemeris

Open Ephemeris

by openephemeris
OverviewSchemaRelated ServersScoreDiscussions
Python
Remote

explore_transit_timeline

Read-onlyIdempotent

Generate a visual, date-ordered transit timeline that shows when transiting planets aspect your natal chart points. Get exact crossing dates, aspects, and retrograde markers for any date range.

Instructions

Generate an interactive Transit Timeline — a vertical, date-ordered list of upcoming transit hits (transiting planets forming a chosen aspect to natal chart positions) over a date range.

Returns a visual timeline with: • Exact crossing dates grouped by month • Transiting planet glyph, the natal point it contacts, and the aspect • Zodiac position of each crossing and retrograde markers • Click any transit for a focused interpretation

ASPECT ANGLES: 0 = conjunction/return (default), 180 = opposition, 90 = square, 120 = trine, 60 = sextile. EFFICIENCY: specify transiting_planets and natal_points to keep compute fast. DEFAULT natal_points: sun, moon, mercury, venus, mars, jupiter, saturn. SEARCH RANGE LIMITS: Explorer/PayG → 1 year; Pro → 5 years; Startup → 10 years.

CREDIT COST: 6 credits per call (natal chart + predictive transit search).

Use this for a rich, interactive transit-forecast experience in MCP Apps-capable hosts (Claude Desktop). Falls back to a text summary in other hosts.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
end_dateYesEnd of the transit search window. ISO 8601 date or zoned datetime; a naive clock time is rejected. Date-only resolves to 12:00 UTC.
start_dateYesStart of the transit search window. ISO 8601 date or zoned datetime; a naive clock time is rejected. Date-only resolves to 12:00 UTC.
aspect_angleNoAspect angle in degrees. 0 = conjunction/return (default), 180 = opposition, 90 = square, 120 = trine, 60 = sextile.
natal_pointsNoNatal point IDs to target, e.g. ['sun','moon','asc','mc','saturn']. Omit for the 7 classical bodies.
natal_datetimeYesISO 8601 datetime; zone required — a `Z`/±HH:MM suffix or the `timezone` argument. Date-only resolves to 12:00 UTC. Full rule: server `instructions`.
natal_latitudeYesLatitude of birth location in decimal degrees. Resolve from a place name with location_search; never recall coordinates from memory.
natal_timezoneNoIANA timezone for the natal birth location (e.g. `America/Chicago`); required when the datetime is naive.
natal_longitudeYesLongitude of birth location in decimal degrees.
transiting_planetsNoTransiting planet IDs to search, e.g. ['saturn','jupiter','uranus','pluto','chiron']. Omit to search all outer planets.
Install Server

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already declare readOnly/idempotent/non-destructive, and the description adds substantial behavioral context: exact return components, credit cost (6 credits per call), search range limits per plan, default natal points, and fallback behavior in non-MCP hosts. This exceeds annotation coverage and helps the agent understand side effects and constraints.

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

Conciseness4/5

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

The description is lengthy but well-structured with a summary, bullet list, and labeled sections for aspects, efficiency, limits, and credit cost. All content is actionable, though some details could be tightened without losing key information.

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?

For a complex tool with no output schema, the description covers inputs, defaults, search limits, credit cost, return content, and host-specific behavior. This is sufficient for an agent to select and invoke the tool correctly.

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 the baseline is 3. The description adds default natal_points, aspect-angle mappings (0, 180, 90, 120, 60), and performance guidance to specify transiting_planets/natal_points, supplementing the schema's 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 opens with 'Generate an interactive Transit Timeline' and clearly specifies a date-ordered list of transit hits with aspect and natal positions. It distinguishes itself from sibling tools like ephemeris_transits by emphasizing the interactive, visual experience and MCP Apps-capable host support.

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?

Explicitly states 'Use this for a rich, interactive transit-forecast experience in MCP Apps-capable hosts' and notes the fallback to a text summary. It also provides efficiency guidance (specify transiting_planets/natal_points) and plan-based search limits, but it does not name alternative tools or conditions to prefer them.

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

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/openephemeris/openephemeris-MCP'

If you have feedback or need assistance with the MCP directory API, please join our Discord server