astroway-mcp

Official

by astroway

Overview Schema Source Related Servers Discussions Admin

TypeScript

Remote

Forecast Calendar

astroway_prognostics_forecast_calendar

Read-onlyIdempotent

Generates a combined forecast calendar of transits, lunar phases, ingresses and retrograde stations for a specified period and natal chart.

Instructions

Generate a combined forecast calendar including transits, lunar phases, ingresses, and retrograde stations for a given period.

[Group: Prognostics] [Endpoint: POST /v1/forecast-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_forecast_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
`year`	No
`cells`	No
`maxAbsTotal`	No
`dailySummary`	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": {
-      "year": {
-        "type": [
-          "number",
-          "null"
-        ]
-      }
-    },
-    "required": [
-      "year"
-    ],
-    "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": {
+      "year": {
+        "type": [
+          "number",
+          "null"
+        ]
+      }
+    },
+    "required": [
+      "year"
+    ],
+    "type": "object"
+  }
+]

Addedv1.6.0Oct 24, 2026

TDQS

B3.4/5.0

Behavior3/5

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

Annotations already establish read-only, idempotent, non-destructive, and closed-world behavior. The description adds useful operational context such as the endpoint and cost, but does not explain authentication, rate limits, or how the combined response is structured beyond listing included event types.

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 is front-loaded in one clear sentence, followed by compact metadata for group, endpoint, and cost. There is little wasted wording, though the period reference remains vague.

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?

The output schema and rich input schema reduce what the description must explain. However, the description omits that the forecast is based on a natal chart and a year, which is non-obvious for a "forecast calendar" and central to correct invocation.

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 input schema already carries the parameter documentation burden. The description adds little beyond "for a given period" and does not clarify the required natal chart data or the year field at the top level.

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 uses a specific verb and resource: "Generate a combined forecast calendar" and lists included event types (transits, lunar phases, ingresses, retrograde stations). The word "combined" distinguishes it from narrower sibling calendar tools, though it does not name them explicitly.

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 by "for a given period" and by calling the output "combined." There is no explicit guidance on when to choose this over tools like astroway_prognostics_transit_calendar or astroway_calendar_ingresses, nor any when-not guidance.

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

Deploy Server