Skip to main content
Glama
igmizo

auseklis

by igmizo

Find Returns

find_returns
Read-onlyIdempotent

Find the exact date and time when a celestial body returns to its natal position, enabling calculation of solar, lunar, and planetary returns for any birth chart.

Instructions

Find the exact moments a body returns to its natal longitude — solar returns (the astrological "birthday", one per year), lunar returns (one per ~27.3 days), or any planetary return (e.g. Saturn return, one per ~29.5 years).

Examples:

  • "My solar return in 2026, born 1990-03-15 15:45 Riga" -> { body: "Sun", natal_datetime: "1990-03-15T15:45", natal_timezone: "Europe/Riga", from_datetime: "2026-01-01", to_datetime: "2027-01-01" }

  • "When is my Saturn return?" -> body: "Saturn" with a multi-year window around ages 27–31.

To cast the full chart for a return moment, pass the returned datetime to compute_natal_chart with the person's current location.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
bodyYesWhich body's return to find, e.g. "Sun", "Saturn".
natal_datetimeYesBirth date and time.
natal_timezoneNoIANA timezone the datetime is local to, e.g. "Europe/Riga" or "America/New_York". Omit when the datetime already carries Z or a UTC offset.
from_datetimeYesStart of the search window.
to_datetimeYesEnd of the search window (max 120 years after start).

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
returnsYes
Behavior4/5

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

Annotations already declare readOnlyHint=true, ensuring safety. The description adds behavioral context: it computes exact moments of return and notes the 120-year window in the schema. No contradictions.

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 front-loaded with purpose, includes concise examples, and avoids waste. Slight redundancy in examples, but overall efficient.

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?

Given the tool's complexity (astrological returns, 5 parameters, annotations, output schema), the description covers purpose, example usage, and chaining with other tools. It does not explain output schema, but that is provided separately.

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 covers 100% of parameters. Description adds value by explaining the body enum with examples, providing guidance on natal_timezone usage, and showing datetime formatting. This surpasses baseline 3.

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's purpose: 'Find the exact moments a body returns to its natal longitude'. It specifies types (solar, lunar, planetary) and distinguishes from sibling tools by focusing on returns.

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 clear usage context through examples and mentions using compute_natal_chart for full charts. It lacks explicit when-not or alternatives, but the context is sufficient.

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/igmizo/auseklis'

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