Skip to main content
Glama
igmizo

auseklis

by igmizo

Find Aspect Times

find_aspect_times
Read-onlyIdempotent

Find exact dates when a transiting planet forms an aspect to a natal point, including multiple hits from retrograde loops. Specify natal position by birth data or longitude.

Instructions

Find the exact moments a transiting body perfects an aspect to a natal position — "when exactly does Saturn square my Sun?" Retrograde loops produce multiple hits (typically three) and each is returned.

The natal position can be given two ways:

  1. natal_datetime (+ natal_timezone) and natal_body — computed for you

  2. natal_longitude directly, if already known

Examples:

  • "When does transiting Saturn square my natal Sun (born 1990-03-15 15:45 Riga)?" -> { transiting_body: "Saturn", aspect: "square", natal_datetime: "1990-03-15T15:45", natal_timezone: "Europe/Riga", natal_body: "Sun", from_datetime: "2026-01-01", to_datetime: "2030-01-01" }

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
aspectYesWhich classical aspect to search for.
natal_bodyNoWhich natal body/point is aspected.
to_datetimeYesEnd of the search window (max 120 years after start).
from_datetimeYesStart of the search window.
natal_datetimeNoBirth date/time (with natal_body).
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.
natal_longitudeNoNatal longitude in degrees, as an alternative to natal_datetime + natal_body.
transiting_bodyYesThe moving body.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
hitsYes
Behavior4/5

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

Annotations declare readOnlyHint=true, idempotentHint=true, destructiveHint=false. The description adds key behavioral context: retrograde loops produce multiple hits (typically three) and explains the two ways to specify the natal position, going beyond the annotation hints.

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 concise, well-structured, and front-loaded. It states the purpose, explains modes, and provides an example without extraneous content.

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 the 8 parameters, 4 required, and presence of an output schema, the description covers core behavior, input alternatives, and retrograde loop behavior adequately. The output schema handles return values, so no further detail needed.

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% with parameter descriptions. The description adds meaning by explaining the two usage modes (natal_datetime + natal_body vs. natal_longitude) and providing an example, which is not evident from the schema alone.

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 specifically states 'Find the exact moments a transiting body perfects an aspect to a natal position', using a specific verb and resource. It clearly differentiates from sibling tools like compute_transits and compute_synastry by focusing on aspect timing.

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 context with examples and explains two input methods. It implicitly guides when to use the tool, but does not explicitly mention when not to use it or compare with alternatives.

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