astroway-mcp

Official

by astroway

Overview Schema Source Related Servers Discussions Admin

TypeScript

Remote

Transit Calendar

astroway_prognostics_transit_calendar

Read-onlyIdempotent

List exact transit-to-natal aspect moments within a date range, returning one event per exact pass so retrograde triple passes appear as three separate events.

Instructions

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)]

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "body": "<body>"
    },
    "name": "astroway_prognostics_transit_calendar"
  }
}

Input Schema

Name	Required	Description	Default
`body`	Yes	Wrapper { natal: ChartInput } used by endpoints that take a base natal plus extra parameters in flat fields.

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 changedv1.6.1Nov 9, 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": {
-            "type": [
-              "number",
-              "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": {
-        "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.",
-        "type": [
-          "number",
-          "null"
-        ]
-      },
-      "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"
-  }
-]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 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": {
+            "type": [
+              "number",
+              "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": {
+        "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.",
+        "type": [
+          "number",
+          "null"
+        ]
+      },
+      "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"
+  }
+]

Addedv1.6.0Oct 24, 2026

TDQS

A3.7/5.0

Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive, so the safety profile is covered; the description instead adds genuinely new behavior — that events are exact hits, one per pass, so a retrograde triple pass yields three separate events. The [Cost: 100 credits (Tier 4)] and endpoint lines add billing and transport context. Ordering of returned events and timezone of the returned moments are not stated, keeping it at 4.

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?

A single front-loaded sentence states purpose and the key output-shape nuance, followed by compact metadata lines for group, endpoint, and cost. No filler or restatement of the title. It is arguably too terse for a 100-credit call, but nothing is wasted.

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 a fully documented input schema, the description only needs to convey what the tool conceptually returns, which it does via 'exact moments ... one event per exact pass'. An agent could call it correctly from this plus structured fields. Minor gaps — event ordering, timezone of returned timestamps, and result caps for long ranges — are the only things missing.

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 schema is unusually rich (natal birth-data rules, maxOrb caveat, aspectAngles subset, transitPlanetIds default). The description adds nothing about any parameter — not the startDate/endDate semantics, not the body wrapper. Baseline 3 is the right ceiling when the schema does all the work.

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 verb and resource — 'List the exact moments of transit-to-natal aspects in a date range' — which is far more precise than a generic 'get transits'. The clause about one event per exact pass further pins down the output granularity. It stops short of naming a sibling (e.g. astroway_prognostics_transits) to differentiate from, so a 4 rather than a 5.

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 implied by the name and the 'date range' scoping: you call this when you want a calendar of exact aspect hits rather than a chart snapshot. There is no explicit when-to-use/when-not guidance and no alternative tool is named, so the agent must infer the boundary against transits, forecast_calendar, and the calendar_* family.

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

Deploy Server