Skip to main content
Glama

Western Astrology MCP Server by RoxyAPI

Secondary progressions calculator - progressed chart, progressed Sun and Moon

post_astrology_progressions
Read-only

Generate the secondary progressed chart for any date using the day-for-a-year key. Each day of ephemeris motion after birth stands in for one year of life. Returns every progressed body with its sign, degree, natal house, motion, and retrograde state, plus the progressed Ascendant and Midheaven via the Naibod arc. The progressed Sun and progressed Moon are the headline timing markers for inner growth and emotional chapters. Secondary progressions API, progressed chart calculator, progressed Sun and Moon, progressed Ascendant and Midheaven.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "date": "1990-07-15",
      "time": "14:30:00",
      "latitude": 40.7128,
      "timezone": "America/New_York",
      "longitude": -74.006,
      "targetDate": "2025-07-15"
    },
    "name": "post_astrology_progressions"
  }
}

Input Schema

NameRequiredDescriptionDefault
dateYesBirth date in YYYY-MM-DD format. Determines planetary positions for the specific calendar day.
langNoResponse language (BCP 47). Supported: en, tr, de, es, hi, pt, fr, ru, zh-Hans, zh-Hant. Defaults to en. Coverage varies by domain, and a field with no translation in the requested language returns English.en
timeYesBirth time in 24-hour HH:MM:SS format. Determines the Ascendant (rising sign) and house cusps. Use 12:00:00 if unknown.
compactNoSet true for the same data in a compact shape: arrays of same-shaped objects arrive columnar as {"__cols":[names],"__rows":[[values]]}. Lossless, typically 40 to 52 percent fewer tokens.
latitudeYesBirth location latitude in decimal degrees (-90 to 90). Positive = North, negative = South.
nodeTypeNoLunar node convention. "mean" is the smoothed average node, which always moves retrograde; "true" is the osculating node, which tracks the real perturbed node, oscillates up to about 1.5 degrees either side of the mean on a 173-day cycle, and can briefly turn direct. Neither is more correct and they almost always fall in the same sign. Applies to the North and South Node. True is the osculating node and the default, because it is what most Western chart software reports; mean is the smoothed node preferred by several evolutionary schools, so pass "mean" to match one. Nothing else in the chart changes, and the two agree on the sign except when the node sits within about 1.8 degrees of a cusp. Defaults to "true".true
timezoneYesTimezone: an IANA name (e.g. "America/New_York", "Europe/London", or `cities[0].timezone` from /location/search) or decimal hours from UTC (e.g. -5 for EST, 5.5 for IST). An IANA name is resolved to the offset in force at the given date and time.
longitudeYesBirth location longitude in decimal degrees (-180 to 180). Positive = East, negative = West.
targetDateYesDate to progress the chart to, in YYYY-MM-DD format. Usually today or a forecast date. The day-for-a-year key turns the elapsed years since birth into the same number of ephemeris days after the birth moment.
houseSystemNoHouse system of the natal chart that every progressed body is placed in. Pass the system the natal chart was drawn in so the house numbers match it. Placidus (default) is the most widely used in Western astrology. Whole Sign assigns one sign per house. Equal divides into 30 degree segments from the Ascendant. Koch emphasizes higher latitudes. Quadrant systems fall back to Whole Sign above the polar circle.placidus

Output Schema

NameRequiredDescriptionDefault
planetsYes
summaryYes
ascendantYes
midheavenYes
targetDateYes
birthDetailsYes
elapsedYearsYes
progressedDateYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / houseSystem
      Added value: +{
      +  "default": "placidus",
      +  "description": "House system of the natal chart that every progressed body is placed in. Pass the system the natal chart was drawn in so the house numbers match it. Placidus (default) is the most widely used in Western astrology. Whole Sign assigns one sign per house. Equal divides into 30 degree segments from the Ascendant. Koch emphasizes higher latitudes. Quadrant systems fall back to Whole Sign above the polar circle.",
      +  "enum": [
      +    "placidus",
      +    "whole-sign",
      +    "equal",
      +    "koch"
      +  ],
      +  "example": "placidus",
      +  "type": "string"
      +}
  2. Changed2 schema fields changed
    • changedInput schema / examples
      Previous value: -[
      -  {
      -    "date": "1990-07-15",
      -    "latitude": 40.7128,
      -    "longitude": -74.006,
      -    "targetDate": "2025-07-15",
      -    "time": "14:30:00",
      -    "timezone": -5
      -  }
      -]New value: +[
      +  {
      +    "date": "1990-07-15",
      +    "latitude": 40.7128,
      +    "longitude": -74.006,
      +    "targetDate": "2025-07-15",
      +    "time": "14:30:00",
      +    "timezone": "America/New_York"
      +  }
      +]
    • changedInput schema / properties / timezone / example
      Previous value: --5New value: +"America/New_York"
  3. Changed1 schema field changed
    • changedInput schema / properties / timezone / description
      Previous value: -"Timezone: IANA name (e.g. \"America/New_York\", \"Europe/London\") OR decimal hours from UTC (e.g. -5 for EST, 1 for CET). IANA strings are resolved to the offset in force at the given date and time, so you can pass `cities[0].timezone` from /location/search directly."New value: +"Timezone: an IANA name (e.g. \"America/New_York\", \"Europe/London\", or `cities[0].timezone` from /location/search) or decimal hours from UTC (e.g. -5 for EST, 5.5 for IST). An IANA name is resolved to the offset in force at the given date and time."
  4. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "properties": {
      +    "ascendant": {
      +      "properties": {
      +        "degree": {
      +          "maximum": 30,
      +          "minimum": 0,
      +          "type": "number"
      +        },
      +        "longitude": {
      +          "maximum": 360,
      +          "minimum": 0,
      +          "type": "number"
      +        },
      +        "sign": {
      +          "type": "string"
      +        },
      +        "signLocalized": {
      +          "type": "string"
      +        }
      +      },
      +      "required": [
      +        "longitude",
      +        "sign",
      +        "degree"
      +      ],
      +      "type": "object"
      +    },
      +    "birthDetails": {
      +      "properties": {
      +        "date": {
      +          "format": "date",
      +          "type": "string"
      +        },
      +        "latitude": {
      +          "maximum": 90,
      +          "minimum": -90,
      +          "type": "number"
      +        },
      +        "longitude": {
      +          "maximum": 180,
      +          "minimum": -180,
      +          "type": "number"
      +        },
      +        "time": {
      +          "format": "time",
      +          "type": "string"
      +        },
      +        "timezone": {
      +          "maximum": 14,
      +          "minimum": -12,
      +          "type": "number"
      +        }
      +      },
      +      "required": [
      +        "date",
      +        "time",
      +        "latitude",
      +        "longitude",
      +        "timezone"
      +      ],
      +      "type": "object"
      +    },
      +    "elapsedYears": {
      +      "type": "number"
      +    },
      +    "midheaven": {
      +      "properties": {
      +        "degree": {
      +          "maximum": 30,
      +          "minimum": 0,
      +          "type": "number"
      +        },
      +        "longitude": {
      +          "maximum": 360,
      +          "minimum": 0,
      +          "type": "number"
      +        },
      +        "sign": {
      +          "type": "string"
      +        },
      +        "signLocalized": {
      +          "type": "string"
      +        }
      +      },
      +      "required": [
      +        "longitude",
      +        "sign",
      +        "degree"
      +      ],
      +      "type": "object"
      +    },
      +    "planets": {
      +      "items": {
      +        "properties": {
      +          "degree": {
      +            "maximum": 30,
      +            "minimum": 0,
      +            "type": "number"
      +          },
      +          "house": {
      +            "maximum": 12,
      +            "minimum": 1,
      +            "type": "integer"
      +          },
      +          "interpretation": {
      +            "type": "string"
      +          },
      +          "isRetrograde": {
      +            "type": "boolean"
      +          },
      +          "longitude": {
      +            "maximum": 360,
      +            "minimum": 0,
      +            "type": "number"
      +          },
      +          "name": {
      +            "type": "string"
      +          },
      +          "nameLocalized": {
      +            "type": "string"
      +          },
      +          "sign": {
      +            "type": "string"
      +          },
      +          "signLocalized": {
      +            "type": "string"
      +          },
      +          "speed": {
      +            "type": "number"
      +          }
      +        },
      +        "required": [
      +          "name",
      +          "longitude",
      +          "sign",
      +          "degree",
      +          "house",
      +          "speed",
      +          "isRetrograde",
      +          "interpretation"
      +        ],
      +        "type": "object"
      +      },
      +      "type": "array"
      +    },
      +    "progressedDate": {
      +      "type": "string"
      +    },
      +    "summary": {
      +      "type": "string"
      +    },
      +    "targetDate": {
      +      "type": "string"
      +    }
      +  },
      +  "required": [
      +    "birthDetails",
      +    "targetDate",
      +    "progressedDate",
      +    "elapsedYears",
      +    "planets",
      +    "ascendant",
      +    "midheaven",
      +    "summary"
      +  ],
      +  "type": "object"
      +}
  5. Changed1 schema field changed
    • changedInput schema / properties / timezone / description
      Previous value: -"Timezone: IANA name (e.g. \"America/New_York\", \"Europe/London\") OR decimal hours from UTC (e.g. -5 for EST, 1 for CET). IANA strings are resolved to the DST-correct offset for the given date, so you can pass `cities[0].timezone` from /location/search directly."New value: +"Timezone: IANA name (e.g. \"America/New_York\", \"Europe/London\") OR decimal hours from UTC (e.g. -5 for EST, 1 for CET). IANA strings are resolved to the offset in force at the given date and time, so you can pass `cities[0].timezone` from /location/search directly."
  6. Changed2 schema fields changed
    • changedInput schema / properties / lang / description
      Previous value: -"Response language (ISO 639-1). Supported: en, tr, de, es, hi, pt, fr, ru. Defaults to en. Languages without translations yet return English."New value: +"Response language (BCP 47). Supported: en, tr, de, es, hi, pt, fr, ru, zh-Hans, zh-Hant. Defaults to en. Coverage varies by domain, and a field with no translation in the requested language returns English."
    • changedInput schema / properties / lang / enum
      Previous value: -[
      -  "en",
      -  "tr",
      -  "de",
      -  "es",
      -  "hi",
      -  "pt",
      -  "fr",
      -  "ru"
      -]New value: +[
      +  "en",
      +  "tr",
      +  "de",
      +  "es",
      +  "hi",
      +  "pt",
      +  "fr",
      +  "ru",
      +  "zh-Hans",
      +  "zh-Hant"
      +]
  7. Changed3 schema fields changed
    • addedInput schema / examples
      Added value: +[
      +  {
      +    "date": "1990-07-15",
      +    "latitude": 40.7128,
      +    "longitude": -74.006,
      +    "targetDate": "2025-07-15",
      +    "time": "14:30:00",
      +    "timezone": -5
      +  }
      +]
    • changedInput schema / properties / compact / description
      Previous value: -"Set true to receive the exact same data in a token-optimized shape that is cheaper for you to read: whitespace is stripped and every array of same-shaped objects is encoded columnar as {\"__cols\":[field names],\"__rows\":[[values]]}, so each field name is sent once instead of once per row. Fully lossless (no field or value is dropped or changed) and typically 40 to 52 percent fewer tokens on large results. Prefer true whenever token or inference cost matters. Default false returns standard indented JSON."New value: +"Set true for the same data in a compact shape: arrays of same-shaped objects arrive columnar as {\"__cols\":[names],\"__rows\":[[values]]}. Lossless, typically 40 to 52 percent fewer tokens."
    • changedInput schema / properties / nodeType / description
      Previous value: -"Lunar node convention. \"mean\" is the smoothed average node, which always moves retrograde; \"true\" is the osculating node, which tracks the real perturbed node, oscillates up to about 1.5 degrees either side of the mean on a 173-day cycle, and can briefly turn direct. Neither is more correct and they almost always fall in the same sign. Applies to the North and South Node. True is what most Western software reports (Astrolabe, Cafe Astrology, TimePassages), which is why it is the default here; astro-seek and the Steven Forrest evolutionary school use mean, so pass \"mean\" to match those. Nothing else in the chart changes, and the two agree on the sign except when the node sits within about 1.8 degrees of a cusp. Defaults to \"true\"."New value: +"Lunar node convention. \"mean\" is the smoothed average node, which always moves retrograde; \"true\" is the osculating node, which tracks the real perturbed node, oscillates up to about 1.5 degrees either side of the mean on a 173-day cycle, and can briefly turn direct. Neither is more correct and they almost always fall in the same sign. Applies to the North and South Node. True is the osculating node and the default, because it is what most Western chart software reports; mean is the smoothed node preferred by several evolutionary schools, so pass \"mean\" to match one. Nothing else in the chart changes, and the two agree on the sign except when the node sits within about 1.8 degrees of a cusp. Defaults to \"true\"."
  8. Changed1 schema field changed
    • addedInput schema / properties / nodeType
      Added value: +{
      +  "default": "true",
      +  "description": "Lunar node convention. \"mean\" is the smoothed average node, which always moves retrograde; \"true\" is the osculating node, which tracks the real perturbed node, oscillates up to about 1.5 degrees either side of the mean on a 173-day cycle, and can briefly turn direct. Neither is more correct and they almost always fall in the same sign. Applies to the North and South Node. True is what most Western software reports (Astrolabe, Cafe Astrology, TimePassages), which is why it is the default here; astro-seek and the Steven Forrest evolutionary school use mean, so pass \"mean\" to match those. Nothing else in the chart changes, and the two agree on the sign except when the node sits within about 1.8 degrees of a cusp. Defaults to \"true\".",
      +  "enum": [
      +    "mean",
      +    "true"
      +  ],
      +  "example": "true",
      +  "type": "string"
      +}
  9. Changed1 schema field changed
    • changedInput schema / properties / compact / description
      Previous value: -"Return the same data in a token-optimized compact shape (minified, with same-shaped arrays encoded columnar) to reduce LLM token cost. Lossless: no fields are dropped. Default false."New value: +"Set true to receive the exact same data in a token-optimized shape that is cheaper for you to read: whitespace is stripped and every array of same-shaped objects is encoded columnar as {\"__cols\":[field names],\"__rows\":[[values]]}, so each field name is sent once instead of once per row. Fully lossless (no field or value is dropped or changed) and typically 40 to 52 percent fewer tokens on large results. Prefer true whenever token or inference cost matters. Default false returns standard indented JSON."
  10. Changed1 schema field changed
    • addedInput schema / properties / compact
      Added value: +{
      +  "default": false,
      +  "description": "Return the same data in a token-optimized compact shape (minified, with same-shaped arrays encoded columnar) to reduce LLM token cost. Lossless: no fields are dropped. Default false.",
      +  "type": "boolean"
      +}
  11. Changed2 schema fields changed
    • changedInput schema / properties / timezone / anyOf
      Previous value: -[
      -  {
      -    "maximum": 14,
      -    "minimum": -14,
      -    "type": "number"
      -  },
      -  {
      -    "pattern": "^[A-Za-z_]+(?:\\/[A-Za-z0-9_+-]+){0,2}$",
      -    "type": "string"
      -  }
      -]New value: +[
      +  {
      +    "maximum": 14,
      +    "minimum": -14,
      +    "type": "number"
      +  },
      +  {
      +    "type": "string"
      +  }
      +]
    • changedInput schema / properties / timezone / description
      Previous value: -"Timezone: decimal hours from UTC (e.g. -5 for EST, 5.5 for IST) OR IANA name (e.g. \"America/New_York\", \"Asia/Kolkata\"). IANA strings are resolved to the DST-correct offset for the given date, so you can pass `cities[0].timezone` from /location/search directly."New value: +"Timezone: IANA name (e.g. \"America/New_York\", \"Europe/London\") OR decimal hours from UTC (e.g. -5 for EST, 1 for CET). IANA strings are resolved to the DST-correct offset for the given date, so you can pass `cities[0].timezone` from /location/search directly."
  12. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so safety is covered; the description adds real substance beyond that by naming the computational method (day-for-a-year key, Naibod arc for Asc/MC) and enumerating what each progressed body carries. It does not mention limits, latency, or behavior at high latitudes, which the schema handles instead.

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 first two sentences are front-loaded and dense with useful meaning, but the closing sentence is an SEO keyword list ("Secondary progressions API, progressed chart calculator...") that repeats terms already stated and adds no decision-relevant 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?

With an output schema present and 100% schema description coverage, the description does not need to document returns or parameters, yet it still explains the output shape and the Naibod arc method. The only gap is routing guidance against the many adjacent natal/timing tools.

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 the baseline is 3, and the description earns a bump by explaining what targetDate actually means mechanically — elapsed years converted into ephemeris days after birth. That conceptual framing is not in the schema text and helps an agent understand the two-date input model.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The opening sentence names a specific verb and resource ("Generate the secondary progressed chart") and explains the day-for-a-year key, which implicitly separates it from transit, solar-arc, and profection siblings. It stops short of naming those siblings, so an agent must still infer the boundary rather than being told it.

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 is only implied: the note that progressed Sun and Moon are "timing markers for inner growth and emotional chapters" hints at interpretive use, but there is no explicit when-to-use or when-not-to-use guidance relative to post_astrology_transits, post_astrology_solar_arc, or post_astrology_profections.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources