RoxyAPI Astrology MCP server

Official

by RoxyAPI

Overview Schema Source Related Servers Discussions Admin

TypeScript

Remote

Annual profections calculator - lord of the year and yearly time lord by age

post_astrology_profections

Read-only

Calculate annual profections and the lord of the year from a birth chart and target date, returning the profected house, sign, ruling planet, and interpretation.

Instructions

Calculate the annual profection and lord of the year for any birth chart and target date using the Hellenistic time lord technique. Each completed year of life advances the rising sign by one whole sign house, activating a new profected house, profected sign, and ruling planet that sets the tone of the year. Returns the age, profected house and sign, the lord of the year with its natal sign and house placement, and a plain language interpretation for traditional and Hellenistic astrology apps.

Input Schema

Name	Required	Description	Default
`date`	Yes	Birth date in YYYY-MM-DD format. Determines planetary positions for the specific calendar day.
`lang`	No	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.	en
`time`	Yes	Birth time in 24-hour HH:MM:SS format. Determines the Ascendant (rising sign) and house cusps. Use 12:00:00 if unknown.
`compact`	No	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.
`latitude`	Yes	Birth location latitude in decimal degrees (-90 to 90). Positive = North, negative = South.
`nodeType`	No	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".	true
`timezone`	Yes	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.
`longitude`	Yes	Birth location longitude in decimal degrees (-180 to 180). Positive = East, negative = West.
`targetDate`	Yes	Date whose profection year you want, in YYYY-MM-DD format. The completed whole years from the birth date to this date select the profected house and sign. Must fall on or after the birth date.
`houseSystem`	No	House system used only to report where the lord of the year sits in the natal chart. The profected house and sign always use whole sign profection from the rising sign. Placidus (default), Whole Sign, Equal, or Koch.	placidus

Output Schema

Name	Required	Description	Default
`age`	Yes
`summary`	Yes
`lordOfYear`	Yes
`targetDate`	Yes
`birthDetails`	Yes
`profectedSign`	Yes
`interpretation`	Yes
`profectedHouse`	Yes
`lordNatalPosition`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedv1.1.2Oct 5, 2026

changedInput schema / examples

Previous value: -[
-  {
-    "date": "1990-07-15",
-    "latitude": 40.7128,
-    "longitude": -74.006,
-    "targetDate": "2025-08-04",
-    "time": "14:30:00",
-    "timezone": -5
-  }
-]New value: +[
+  {
+    "date": "1990-07-15",
+    "latitude": 40.7128,
+    "longitude": -74.006,
+    "targetDate": "2025-08-04",
+    "time": "14:30:00",
+    "timezone": "America/New_York"
+  }
+]

changedInput schema / properties / timezone / example

Previous value: --5New value: +"America/New_York"

First observedv0.1.0Oct 4, 2026

TDQS

A4/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 the safety profile is covered. The description adds real value beyond that by spelling out what the calculation produces (age, profected house/sign, lord of the year with natal sign and house, plain-language interpretation) and the technique that drives it, though it says nothing about auth, rate limits, or edge cases (e.g. targetDate before birth, which the schema handles).

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?

Three sentences, front-loaded with the core action and output, with no filler. It is slightly longer than strictly necessary given the schema and output schema carry the detail, but every sentence conveys real 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?

With an output schema present, annotations covering the read-only profile, and full parameter documentation in the schema, the description only needs to establish purpose, mechanism, and output gist — all of which it does. An agent has everything needed to invoke it correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the schema already documents all ten parameters in detail. The description adds only conceptual framing (birth chart + target date) and no parameter-specific syntax or format detail beyond what the schema provides, so the baseline of 3 applies.

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?

States a specific verb+resource ('Calculate the annual profection and lord of the year for any birth chart and target date') and names the distinctive Hellenistic time-lord technique, which cleanly separates it from siblings like progressions, solar return, or transits. The one-line mechanism (each completed year advances the rising sign by one whole-sign house) makes the tool's scope unambiguous.

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?

The description explains the technique well but never states when to choose this tool over alternatives such as post_astrology_progressions, post_astrology_solar_return, or post_astrology_planetary_returns, and gives no exclusions or prerequisites. Usage is only implied by the technique's definition.

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

Deploy Server