Skip to main content
Glama

dev_call

Read-only

Make direct API calls to any allowlisted Open Ephemeris endpoint for custom astrological computations, bypassing typed tools when needed.

Instructions

Call any allowlisted Open Ephemeris API endpoint directly. This is the power-user escape hatch — use the typed tools (ephemeris_natal_chart, ephemeris_transits, etc.) first for common operations. Call dev_list_allowed to see all currently available endpoint paths.

AUTH: Set OPENEPHEMERIS_API_KEY in your environment. See openephemeris.com/dashboard for active plan limits.

CREDIT COSTS: • Standard chart math (natal, progressed, bazi, vedic, iching): 1 credit • Human Design: 2 credits • Visualization rendering (chart-wheel, bi-wheel, charts/*): 2 credits • Comparative math (synastry, composite, overlay): 3 credits • Predictive ops (transits/search, returns): 5 credits • Predictive transit-chart: 1 credit • ACG / astrocartography: 10 credits (acg/hits: 15 credits) • Calendar endpoints: 10 credits • Catalog / metadata / health endpoints: 0 credits • Compute surcharge: requests > 30s add 1 credit per 30s (predictive, acg, calendar, electional) • format=llm (token-optimized output): available on all tiers

COMMON CALLS: POST /ephemeris/natal-chart — Full natal chart (body: {subject: {name: 'Name', birth_datetime: {iso: '1990-04-15T14:30:00-05:00'}, birth_location: {latitude: {decimal: 40.0}, longitude: {decimal: -70.0}, timezone: {}}}}) POST /ephemeris/natal/batch — Up to 50 natal charts in one request POST /ephemeris/relocation — Relocated chart (same natal, new location) POST /predictive/transits/search — Transit event search over a date range POST /predictive/returns/solar — Solar return chart POST /predictive/returns/lunar — Lunar return chart POST /comparative/synastry — Two-person synastry chart POST /comparative/composite — Composite (midpoint) chart POST /human-design/chart — Full HD chart (body: {birth_datetime_utc: '1990-04-15T19:30:00Z'}) — lat/lon optional POST /time/julian-day — Convert date to JD (body: {year: 1987, month: 7, day: 15, hour: 14, minute: 1}) GET /ephemeris/moon/phase — Current/queried moon phase GET /ephemeris/moon/void-of-course — Next void-of-course period GET /ephemeris/agro/daily — Biodynamic farming day quality GET /ephemeris/agro/calendar — Multi-day biodynamic calendar GET /ephemeris/agro/void-of-course — Biodynamic VoC periods GET /eclipse/next-visible — Next eclipse visible from a location (query: lat, lon, type=solar|lunar) GET /eclipse/solar/global — Next global solar eclipse (query: date=YYYY-MM-DD) GET /eclipse/solar/local — Local solar eclipse (query: lat, lon) GET /tidal/forcing — Gravitational tidal forcing index POST /acg/power-lines — Astrocartography power lines (lat/lon GeoJSON) POST /acg/hits — ACG power at a specific location GET /calendar/astrology/moon-phases — Moon phase calendar for a date range GET /location/autocomplete — Geocode a place name (query: q=City Name) POST /timezone/lookup — Resolve timezone + UTC offset for a location POST /chinese/bazi — Chinese Ba Zi (Four Pillars) chart (body: {year, month, day, hour}) GET /chinese/zodiac — Chinese zodiac year element/animal POST /vedic/chart — Vedic (Jyotish) natal chart (body: {datetime_utc, latitude, longitude}) GET /catalogs/bodies — List all supported celestial bodies

BINARY RESPONSES: • Binary/image endpoints return {content_type, content_length, encoding, data_base64} so callers can decode bytes deterministically.

ECLIPSE NOTE: Eclipse endpoints accept format=llm via the query param like other endpoints.

format=llm NOTE: Add query: {format: 'llm'} to natal/synastry/composite/HD endpoints for compact columnar output optimized for LLM token budgets (availability depends on your current plan).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
methodYesHTTP method
pathYesAbsolute API path (e.g., /ephemeris/natal-chart)
queryNoQuery params for GET requests (optional)
bodyNoJSON body for POST/PUT/PATCH (optional)
presetNoConvenience: if provided, set query.preset (optional).
formatNoConvenience: if provided, set query.format (optional). 'llm' is canonical; 'llm_v2' is accepted as a legacy alias.
output_modeNoLegacy convenience (deprecated): if provided, set query.output_mode and also map to query.preset/query.format when possible.
Behavior4/5

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

Annotations declare readOnlyHint=true and destructiveHint=false, and the description does not contradict these. It adds significant behavioral context beyond annotations, including credit costs per endpoint type, binary response format, and format=llm optimization, which helps the agent understand usage implications.

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

Conciseness3/5

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

The description is well-structured with sections (AUTH, CREDIT COSTS, etc.) and front-loaded purpose. However, it is quite verbose with many example calls and detailed credit tables, which could be trimmed without losing essential information.

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 complex tool with many endpoints and parameters, the description covers authentication, credits, common calls, and special notes. It lacks a generic response format explanation for non-binary endpoints, but the detail on binary responses and format=llm mitigates this gap.

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?

Input schema has 100% description coverage, so the baseline is 3. The description provides example bodies for common calls and notes like format=llm, but these add only marginal value beyond 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 clearly states the tool calls any allowlisted Open Ephemeris API endpoint directly, positioning it as a power-user escape hatch. It distinguishes itself from typed tools by instructing to use them first, making the purpose unambiguous.

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?

The description explicitly advises to use typed tools first and mentions dev_list_allowed for endpoint discovery. It provides credit costs and common calls, giving clear context for when to use this tool, though it does not list specific exclusions beyond preferring typed tools.

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

Install Server

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