Skip to main content
Glama
igmizo

auseklis

by igmizo

Compute Secondary Progressions

compute_progressions
Read-onlyIdempotent

Compute a secondary-progressed chart to reveal how your natal chart evolves over time using the day-for-a-year method. Shows progressed positions and aspects to natal planets.

Instructions

Compute a secondary-progressed chart: the natal chart advanced one ephemeris day per year of life (the standard "day-for-a-year" method). Shows how the chart has symbolically evolved by a given date.

Examples:

  • "My progressed chart for today, born 1990-03-15 15:45 Riga" -> { natal_datetime: "1990-03-15T15:45", natal_timezone: "Europe/Riga" } (target_datetime defaults to now)

Returns progressed positions and the aspects progressed bodies make to natal bodies. The progressed Moon (~1 sign per 2.5 years) and progressed Sun (~1° per year) carry the most interpretive weight.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
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.
target_datetimeNoDate to progress to. Defaults to now.
target_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.
zodiacNoZodiac frame: tropical (Western default), sidereal-lahiri (Vedic), or sidereal-fagan-bradley (Western sidereal).tropical

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
natalUtcYes
targetUtcYes
progressedUtcYes
ageYearsYes
positionsYes
aspectsToNatalYes
Behavior4/5

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

Annotations indicate readOnly, destructive, idempotent, and openWorld hints. The description adds behavioral context by detailing return values (progressed positions and aspects) and interpretive weight of the Moon and Sun, which goes beyond the structured annotations.

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 with no wasted words, front-loads the main purpose, and uses a clear example structure. Every sentence contributes meaningful 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?

Given the tool's complexity and presence of an output schema, the description adequately explains the concept and usage. It could mention timezone handling more explicitly, but is largely complete.

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 description coverage is 100%, so baseline is 3. The description adds value through a concrete usage example, clarifying default target_datetime behavior, and explaining the zodiac parameter, elevating semantics slightly.

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 computes secondary progressions and explains the 'day-for-a-year' method. It distinguishes from siblings like compute_natal_chart and compute_transits by specifying it advances the natal chart symbolically.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage context is implied through examples and explanation of default behavior, but no explicit when-to-use or when-not-to-use guidance is provided. Siblings exist for different astrological computations, yet no comparisons are made.

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