AstroWay Astrology API (full catalogue)

Transit Calendar

astroway_prognostics_transit_calendar

Read-onlyIdempotent

List the exact moments of transit-to-natal aspects in a date range, one event per exact pass, so a retrograde triple pass gives three events.

[Group: Prognostics] [Endpoint: POST /v1/transit-calendar] [Cost: 100 credits (Tier 4)]

Input Schema

Name	Required	Description
`body`	Yes	Wrapper { natal: ChartInput } used by endpoints that take a base natal plus extra parameters in flat fields.
`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
`count`	No
`events`	No
`maxOrb`	No
`endDate`	No
`startDate`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 15, 2026

changedInput schema / properties / body / allOf

Previous value: -[
-  {
-    "description": "Wrapper { natal: ChartInput } used by endpoints that take a base natal plus extra parameters in flat fields.",
-    "properties": {
-      "natal": {
-        "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"
-      }
-    },
-    "required": [
-      "natal"
-    ],
-    "type": "object"
-  },
-  {
-    "properties": {
-      "aspectAngles": {
-        "items": {
-          "anyOf": [
-            {
-              "maximum": 360,
-              "minimum": 0,
-              "type": "number"
-            },
-            {
-              "type": "null"
-            }
-          ]
-        },
-        "maxItems": 64,
-        "type": "array"
-      },
-      "endDate": {
-        "pattern": "^\\d{4}-\\d{2}-\\d{2}$",
-        "type": "string"
-      },
-      "maxOrb": {
-        "anyOf": [
-          {
-            "type": "number"
-          },
-          {
-            "type": "null"
-          }
-        ]
-      },
-      "startDate": {
-        "pattern": "^\\d{4}-\\d{2}-\\d{2}$",
-        "type": "string"
-      },
-      "transitPlanetIds": {
-        "items": {
-          "anyOf": [
-            {
-              "maximum": 9007199254740991,
-              "minimum": 0,
-              "type": "integer"
-            },
-            {
-              "type": "null"
-            }
-          ]
-        },
-        "maxItems": 32,
-        "type": "array"
-      }
-    },
-    "required": [
-      "startDate",
-      "endDate"
-    ],
-    "type": "object"
-  }
-]New value: +[
+  {
+    "description": "Wrapper { natal: ChartInput } used by endpoints that take a base natal plus extra parameters in flat fields.",
+    "properties": {
+      "natal": {
+        "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"
+      }
+    },
+    "required": [
+      "natal"
+    ],
+    "type": "object"
+  },
+  {
+    "properties": {
+      "aspectAngles": {
+        "description": "Subset of 0, 60, 90, 120, 180 (the default is all five). Other angles match nothing and answer 400.",
+        "items": {
+          "anyOf": [
+            {
+              "maximum": 360,
+              "minimum": 0,
+              "type": "number"
+            },
+            {
+              "type": "null"
+            }
+          ]
+        },
+        "maxItems": 64,
+        "type": "array"
+      },
+      "endDate": {
+        "pattern": "^\\d{4}-\\d{2}-\\d{2}$",
+        "type": "string"
+      },
+      "maxOrb": {
+        "anyOf": [
+          {
+            "type": "number"
+          },
+          {
+            "type": "null"
+          }
+        ],
+        "description": "Accepted and echoed back, but it does not filter anything: every event is an exact hit, found by the sign change of the offset and refined by bisection, so its orb is 0. Must be in (0, 10] if sent."
+      },
+      "startDate": {
+        "pattern": "^\\d{4}-\\d{2}-\\d{2}$",
+        "type": "string"
+      },
+      "transitPlanetIds": {
+        "description": "Transiting bodies, ids 0 and 2-9 (Sun, Mercury to Pluto; the Moon is excluded). Default: all nine.",
+        "items": {
+          "anyOf": [
+            {
+              "maximum": 9007199254740991,
+              "minimum": 0,
+              "type": "integer"
+            },
+            {
+              "type": "null"
+            }
+          ]
+        },
+        "maxItems": 32,
+        "type": "array"
+      }
+    },
+    "required": [
+      "startDate",
+      "endDate"
+    ],
+    "type": "object"
+  }
+]

First observedOct 5, 2026

TDQS

A3.5/5.0

Behavior3/5

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

Annotations already cover readOnly, idempotent, non-destructive and closed-world, so the safety profile is settled. The description adds two pieces of context beyond that - the 100-credit Tier 4 cost and the event-per-pass counting behavior - which is useful for planning a paid call, but it says nothing about auth, rate limits, or pagination.

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?

One dense sentence front-loads the purpose and the event-count semantics, followed by three compact metadata lines (group, endpoint, cost) that each carry distinct, useful information. Nothing is padded or repeated.

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?

The schema documents the natal chart requirements, aspect defaults, transit body defaults and the inert maxOrb in unusual depth, and an output schema exists so return values need no explanation here. For a tool whose per-parameter contracts are this thoroughly specified in structured fields, the description covers what it must.

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 effectively 100%, and the nested natal/chart fields, aspectAngles, transitPlanetIds and maxOrb all carry their own detailed prose in the schema. The description only implies 'date range' filtering; it adds no syntax, defaults, or constraints beyond the schema, so the baseline 3 applies.

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?

States a specific verb and resource - listing exact transit-to-natal aspect moments within a date range - and the clause about 'one event per exact pass, so a retrograde triple pass gives three events' pins down the granularity of the output. This clearly separates it from a continuous transit-position tool in spirit, but it never names the close sibling astroway_prognostics_transits, leaving that disambiguation to inference.

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?

The description gives no when-to-use guidance, no prerequisites, and no named alternative. It never says to prefer this over astroway_prognostics_transits or astroway_prognostics_forecast_calendar, nor when a calendar of exact hits rather than a positions listing is the right choice.

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?