Skip to main content
Glama

ephemeris_solar_return

Read-only

Calculate the exact Solar Return date/time and receive the Solar Return chart for the year ahead, based on the Sun's return to its natal ecliptic longitude.

Instructions

Calculate the exact Solar Return date/time — when the Sun returns to its natal ecliptic longitude (happens once per year near the birthday). Returns the Solar Return chart for the year ahead.

CREDIT COST: 5 credits per call.

TARGET DATE: Provide target_datetime near the desired birthday year. If omitted, defaults to the current year's solar return.

EXAMPLE: Solar return for someone born 1985-06-21 (current year): birth_datetime='1985-06-21T14:00:00Z'

EXAMPLE: Solar return for 2027 specifically: birth_datetime='1985-06-21T14:00:00Z', target_datetime='2027-01-01T00:00:00Z'

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
birth_datetimeYesISO 8601 birth date/time. Include offset or Z (e.g. '1985-06-21T14:00:00-05:00').
target_datetimeNoDate/time near which to find the Solar Return (ISO 8601 with offset or Z). Defaults to approximately 1 year from now if omitted.
birth_latitudeNoBirth latitude in decimal degrees (optional, for location context).
birth_longitudeNoBirth longitude in decimal degrees (optional, for location context).
return_latitudeNoLocation latitude for the return chart (optional, if different from birth location).
return_longitudeNoLocation longitude for the return chart (optional).
include_visualNoWhen true, renders the solar return chart wheel as an SVG and embeds it in the response. The chart image will display in the conversation alongside the data. Costs 2 additional credits on top of the base call cost.
visual_configNoOptional rendering preferences (only used when include_visual=true).
Behavior5/5

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

Annotations already declare readOnlyHint=true, and the description adds credit cost, default behavior for target_datetime, and the optional visual config. No contradictions. The description fully informs about non-destructive read operation and additional costs.

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 well-structured with clear sections (CREDIT COST, TARGET DATE, EXAMPLE). It is slightly verbose with multiple examples, but each sentence adds value. Could be condensed slightly without losing 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?

Given no output schema, the description adequately explains that the tool returns the Solar Return chart. It covers all parameters, optional features like visual config, and cost implications. Complete for decision-making.

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 baseline is 3. The description adds value by explaining the default for target_datetime and providing concrete examples. It also clarifies that birth_latitude/birth_longitude are optional and return_latitude/return_longitude for location context.

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 that the tool calculates the Solar Return date/time and returns the chart. It uses specific verb+resource ('Calculate the exact Solar Return date/time'), and distinguishes itself from siblings like ephemeris_lunar_return by focusing on Sun's return to natal ecliptic longitude.

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 provides context on when to use (near birthday) and includes examples for different scenarios. It does not explicitly mention when not to use or list alternatives, but the examples and context make usage clear. Could be improved by noting that this is for solar returns only, not lunar or other returns.

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