AstroWay Astrology API (full catalogue)

Profections Detail

astroway_helb_profections_detail

Read-onlyIdempotent

Annual profection year-lord with full classical condition.

[Group: Hellenistic: Brennan tradition] [Endpoint: POST /v1/hellenistic/brennan/profections-detail] [Cost: 10 credits (Tier 1)]

(Cursor-friendly alias for astroway_hellenistic_brennan_profections_detail.)

Input Schema

Name	Required	Description
`body`	Yes	Birth data for a single natal chart. Required: date (YYYY-MM-DD), time (HH:mm:ss), latitude and longitude in decimal degrees. The short forms lat, lon, lng and tz are rejected with 400 INVALID_FIELD; pass the full names. timezoneOffset is hours from UTC and defaults to 0, meaning UTC; send timezone instead (an IANA name such as Europe/Kyiv, or auto) and the offset for that date is worked out, summer time included. city is a display label only: nothing here geocodes it, so it never stands in for coordinates. houseSystem is a single house-system letter, P by default; a name such as "Placidus" is refused, and the case matters because I and i are two different Sunshine systems.
`fields`	No	Compact mode: comma-separated dotted paths to keep, relative to `data`, e.g. "planets.name,planets.longitude,houses.cusp". Omit for the whole response.
`precision`	No	Compact mode: round fractional numbers to this many decimals. Longitudes carry 14 by default; 2 is finer than any chart is drawn.

Output Schema

Name	Required	Description	Default
`source`	No
`ageYear`	No
`doctrine`	No
`yearLord`	No
`disclaimer`	No
`yearEndDate`	No
`profectedSign`	No
`yearStartDate`	No
`monthlyProfections`	No
`yearLordNatalContext`	No
`profectedHouseFromAsc`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedNov 6, 2026

changedInput schema / properties / body / allOf

Previous value: -[
-  {
-    "additionalProperties": {
-      "anyOf": [
-        {},
-        {
-          "type": "null"
-        }
-      ]
-    },
-    "description": "Birth data for a single natal chart. Required: date (YYYY-MM-DD), time (HH:mm:ss), latitude and longitude in decimal degrees. The short forms lat, lon, lng and tz are rejected with 400 INVALID_FIELD; pass the full names. timezoneOffset is hours from UTC and defaults to 0, meaning UTC; send timezone instead (an IANA name such as Europe/Kyiv, or auto) and the offset for that date is worked out, summer time included. city is a display label only: nothing here geocodes it, so it never stands in for coordinates. houseSystem is a single Swiss Ephemeris letter, P by default; a name such as \"Placidus\" is refused, and the case matters because I and i are two different Sunshine systems.",
-    "properties": {
-      "ayanamsa": {
-        "description": "Sidereal school by name. Lahiri when omitted. Equivalent to ayanamsaId; send either.",
-        "enum": [
-          "fagan-bradley",
-          "lahiri",
-          "de-luce",
-          "raman",
-          "krishnamurti",
-          "kp",
-          "yukteshwar",
-          "jn-bhasin",
-          "true-citra",
-          "djwhal-khul"
-        ],
-        "type": "string"
-      },
-      "ayanamsaId": {
-        "anyOf": [
-          {
-            "type": "number"
-          },
-          {
-            "type": "null"
-          }
-        ]
-      },
-      "city": {
-        "default": "",
-        "type": "string"
-      },
-      "cosmogram": {
-        "type": "boolean"
-      },
-      "date": {
-        "pattern": "^\\d{4}-\\d{2}-\\d{2}$",
-        "type": "string"
-      },
-      "houseSystem": {
-        "default": "P",
-        "enum": [
-          "P",
-          "K",
-          "R",
-          "C",
-          "E",
-          "W",
-          "B",
-          "M",
-          "O",
-          "A",
-          "T",
-          "V",
-          "D",
-          "F",
-          "G",
-          "H",
-          "I",
-          "i",
-          "L",
-          "N",
-          "Q",
-          "S",
-          "U",
-          "X",
-          "Y"
-        ],
-        "type": "string"
-      },
-      "latitude": {
-        "maximum": 90,
-        "minimum": -90,
-        "type": "number"
-      },
-      "longitude": {
-        "maximum": 180,
-        "minimum": -180,
-        "type": "number"
-      },
-      "name": {
-        "default": "",
-        "type": "string"
-      },
-      "time": {
-        "pattern": "^\\d{2}:\\d{2}(:\\d{2})?$",
-        "type": "string"
-      },
-      "timezone": {
-        "description": "IANA zone name such as Europe/Kyiv, or auto to look the zone up from latitude and longitude. The server takes the offset that zone kept at this local date and time, summer time included, and uses it in place of timezoneOffset. A clock time that happened twice takes the first occurrence; one skipped when clocks went forward takes the offset from before the change. Abbreviations such as EST are refused. Before 1970 the tz database is not reliable for every place, so send timezoneOffset when the local clock is known.",
-        "type": "string"
-      },
-      "timezoneOffset": {
-        "anyOf": [
-          {
-            "maximum": 14,
-            "minimum": -14,
-            "type": "number"
-          },
-          {
-            "type": "null"
-          }
-        ],
-        "default": 0,
-        "description": "Hours from UTC at the given moment, not minutes. Fractional zones are hours too: 5.5 for India, 5.75 for Nepal, -3.5 for Newfoundland. Defaults to 0, meaning UTC. Ignored when timezone is sent."
-      },
-      "zodiacType": {
-        "enum": [
-          "tropical",
-          "sidereal"
-        ],
-        "type": "string"
-      }
-    },
-    "required": [
-      "date",
-      "time",
-      "latitude",
-      "longitude"
-    ],
-    "type": "object"
-  },
-  {
-    "additionalProperties": {
-      "anyOf": [
-        {},
-        {
-          "type": "null"
-        }
-      ]
-    },
-    "properties": {
-      "targetAge": {
-        "anyOf": [
-          {
-            "maximum": 120,
-            "minimum": 0,
-            "type": "integer"
-          },
-          {
-            "type": "null"
-          }
-        ]
-      }
-    },
-    "required": [
-      "targetAge"
-    ],
-    "type": "object"
-  }
-]New value: +[
+  {
+    "additionalProperties": {
+      "anyOf": [
+        {},
+        {
+          "type": "null"
+        }
+      ]
+    },
+    "description": "Birth data for a single natal chart. Required: date (YYYY-MM-DD), time (HH:mm:ss), latitude and longitude in decimal degrees. The short forms lat, lon, lng and tz are rejected with 400 INVALID_FIELD; pass the full names. timezoneOffset is hours from UTC and defaults to 0, meaning UTC; send timezone instead (an IANA name such as Europe/Kyiv, or auto) and the offset for that date is worked out, summer time included. city is a display label only: nothing here geocodes it, so it never stands in for coordinates. houseSystem is a single house-system letter, P by default; a name such as \"Placidus\" is refused, and the case matters because I and i are two different Sunshine systems.",
+    "properties": {
+      "ayanamsa": {
+        "description": "Sidereal school by name. Lahiri when omitted. Equivalent to ayanamsaId; send either.",
+        "enum": [
+          "fagan-bradley",
+          "lahiri",
+          "de-luce",
+          "raman",
+          "krishnamurti",
+          "kp",
+          "yukteshwar",
+          "jn-bhasin",
+          "true-citra",
+          "djwhal-khul"
+        ],
+        "type": "string"
+      },
+      "ayanamsaId": {
+        "anyOf": [
+          {
+            "type": "number"
+          },
+          {
+            "type": "null"
+          }
+        ]
+      },
+      "city": {
+        "default": "",
+        "type": "string"
+      },
+      "cosmogram": {
+        "type": "boolean"
+      },
+      "date": {
+        "pattern": "^\\d{4}-\\d{2}-\\d{2}$",
+        "type": "string"
+      },
+      "houseSystem": {
+        "default": "P",
+        "enum": [
+          "P",
+          "K",
+          "R",
+          "C",
+          "E",
+          "W",
+          "B",
+          "M",
+          "O",
+          "A",
+          "T",
+          "V",
+          "D",
+          "F",
+          "G",
+          "H",
+          "I",
+          "i",
+          "L",
+          "N",
+          "Q",
+          "S",
+          "U",
+          "X",
+          "Y"
+        ],
+        "type": "string"
+      },
+      "latitude": {
+        "maximum": 90,
+        "minimum": -90,
+        "type": "number"
+      },
+      "longitude": {
+        "maximum": 180,
+        "minimum": -180,
+        "type": "number"
+      },
+      "name": {
+        "default": "",
+        "type": "string"
+      },
+      "time": {
+        "pattern": "^\\d{2}:\\d{2}(:\\d{2})?$",
+        "type": "string"
+      },
+      "timezone": {
+        "description": "IANA zone name such as Europe/Kyiv, or auto to look the zone up from latitude and longitude. The server takes the offset that zone kept at this local date and time, summer time included, and uses it in place of timezoneOffset. A clock time that happened twice takes the first occurrence; one skipped when clocks went forward takes the offset from before the change. Abbreviations such as EST are refused. Before 1970 the tz database is not reliable for every place, so send timezoneOffset when the local clock is known.",
+        "type": "string"
+      },
+      "timezoneOffset": {
+        "anyOf": [
+          {
+            "maximum": 14,
+            "minimum": -14,
+            "type": "number"
+          },
+          {
+            "type": "null"
+          }
+        ],
+        "default": 0,
+        "description": "Hours from UTC at the given moment, not minutes. Fractional zones are hours too: 5.5 for India, 5.75 for Nepal, -3.5 for Newfoundland. Defaults to 0, meaning UTC. Ignored when timezone is sent."
+      },
+      "zodiacType": {
+        "enum": [
+          "tropical",
+          "sidereal"
+        ],
+        "type": "string"
+      }
+    },
+    "required": [
+      "date",
+      "time",
+      "latitude",
+      "longitude"
+    ],
+    "type": "object"
+  },
+  {
+    "additionalProperties": {
+      "anyOf": [
+        {},
+        {
+          "type": "null"
+        }
+      ]
+    },
+    "properties": {
+      "targetAge": {
+        "anyOf": [
+          {
+            "maximum": 120,
+            "minimum": 0,
+            "type": "integer"
+          },
+          {
+            "type": "null"
+          }
+        ]
+      }
+    },
+    "required": [
+      "targetAge"
+    ],
+    "type": "object"
+  }
+]

changedInput schema / properties / body / description

Previous value: -"Birth data for a single natal chart. Required: date (YYYY-MM-DD), time (HH:mm:ss), latitude and longitude in decimal degrees. The short forms lat, lon, lng and tz are rejected with 400 INVALID_FIELD; pass the full names. timezoneOffset is hours from UTC and defaults to 0, meaning UTC; send timezone instead (an IANA name such as Europe/Kyiv, or auto) and the offset for that date is worked out, summer time included. city is a display label only: nothing here geocodes it, so it never stands in for coordinates. houseSystem is a single Swiss Ephemeris letter, P by default; a name such as \"Placidus\" is refused, and the case matters because I and i are two different Sunshine systems."New value: +"Birth data for a single natal chart. Required: date (YYYY-MM-DD), time (HH:mm:ss), latitude and longitude in decimal degrees. The short forms lat, lon, lng and tz are rejected with 400 INVALID_FIELD; pass the full names. timezoneOffset is hours from UTC and defaults to 0, meaning UTC; send timezone instead (an IANA name such as Europe/Kyiv, or auto) and the offset for that date is worked out, summer time included. city is a display label only: nothing here geocodes it, so it never stands in for coordinates. houseSystem is a single house-system letter, P by default; a name such as \"Placidus\" is refused, and the case matters because I and i are two different Sunshine systems."

First observedOct 5, 2026

TDQS

B3.2/5.0

Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world behavior, so the safety profile is fully covered. The description adds genuinely new context that annotations cannot convey: the 10-credit Tier 1 cost and the concrete endpoint. It does not say what happens when `targetAge` is omitted (nullable in schema) or how the classical condition is reported, but with annotations plus an output schema that gap is modest.

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 purpose sentence is front-loaded and short, and the bracketed group/endpoint/cost lines are scannable structured metadata rather than prose. Slight redundancy in restating the canonical tool name, but no wasted narrative.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With an output schema, rich annotations, and a fully documented input schema, the description only needs to frame the technique and cost, which it does. It stops short of explaining the `targetAge` semantics or how this differs from the near-identical generic profections tool, which are the two things an agent would still have to guess.

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% and the embedded birth-data description is unusually thorough (formats, rejected short names, timezone behavior, house-system letters), so the schema carries parameter meaning on its own. The tool description adds nothing about the one parameter unique to this tool, `targetAge`, which determines which profection year is returned.

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 description names a specific technique and output: the annual profection year-lord together with its full classical condition, plus the Brennan tradition group. The parenthetical clarifies that this is a cursor-friendly alias of `astroway_hellenistic_brennan_profections_detail`, which lets an agent distinguish it from that sibling, though it never explains how it differs from the generic `astroway_prognostics_profections`.

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

Usage Guidelines2/5

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

There is no statement of when to use this tool versus alternatives such as `astroway_prognostics_profections`, `astroway_hellenistic_brennan_time_lord_stack`, or the zodiacal releasing tools, and no prerequisites are given. The only usage-relevant fact is the alias equivalence note, which implies 'either name works' but does not guide selection.

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

All AstroWay Astrology API (full catalogue) tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?