Astrology Forecast MCP Server by RoxyAPI

Significant dates - High-significance cross-domain forecast highlights

post_forecast_significant_dates

Read-only

Return only the high-significance dates from the merged cross-domain forecast for a single birth subject: the rare outer-planet exact transit aspects, slow-planet sign ingresses, retrograde stations, and Vimshottari mahadasha and antardasha changes that mark genuine turning points. Defaults to a significance floor of 70 so the response is a short list of the most meaningful upcoming dates. Built for what-is-coming highlights, timing alerts, and at-a-glance forecast strips.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`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
`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.
`domains`	No	Which forecast domains to consider before filtering by significance. Defaults to all three.
`endDate`	No	Last day of the window in YYYY-MM-DD format. Defaults to startDate plus 30 days. Clamped to a maximum of 90 days from startDate.
`birthData`	Yes	The single birth subject this forecast is built for. One object only, never an array.
`startDate`	No	First day of the window in YYYY-MM-DD format. Defaults to today in UTC.
`domainWeights`	No	Per-domain significance multipliers applied before the significance floor and event cap. Bias which domains survive filtering and the cap. Omitted domains default to a weight of 1. Valid keys are western, vedic, and biorhythm.
`minSignificance`	No	Significance floor from 0 to 100 for what counts as a significant date. Defaults to 70.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`count`	Yes
`events`	Yes
`endDate`	Yes
`birthData`	Yes
`startDate`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedSep 20, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "birthData": {
+      "properties": {
+        "date": {
+          "format": "date",
+          "type": "string"
+        },
+        "latitude": {
+          "default": 0,
+          "maximum": 90,
+          "minimum": -90,
+          "type": "number"
+        },
+        "longitude": {
+          "default": 0,
+          "maximum": 180,
+          "minimum": -180,
+          "type": "number"
+        },
+        "time": {
+          "format": "time",
+          "type": "string"
+        },
+        "timezone": {
+          "type": "number"
+        }
+      },
+      "required": [
+        "date",
+        "time",
+        "timezone"
+      ],
+      "type": "object"
+    },
+    "count": {
+      "type": "number"
+    },
+    "endDate": {
+      "type": "string"
+    },
+    "events": {
+      "items": {
+        "properties": {
+          "aspect": {
+            "type": "string"
+          },
+          "body": {
+            "type": "string"
+          },
+          "date": {
+            "type": "string"
+          },
+          "datetime": {
+            "type": "string"
+          },
+          "description": {
+            "type": "string"
+          },
+          "domain": {
+            "enum": [
+              "western",
+              "vedic",
+              "biorhythm"
+            ],
+            "type": "string"
+          },
+          "kind": {
+            "enum": [
+              "penumbral",
+              "partial",
+              "annular",
+              "total"
+            ],
+            "type": "string"
+          },
+          "obscuration": {
+            "type": "number"
+          },
+          "orb": {
+            "type": "number"
+          },
+          "phase": {
+            "enum": [
+              "new-moon",
+              "full-moon"
+            ],
+            "type": "string"
+          },
+          "significance": {
+            "type": "number"
+          },
+          "station": {
+            "enum": [
+              "retrograde",
+              "direct"
+            ],
+            "type": "string"
+          },
+          "target": {
+            "type": "string"
+          },
+          "type": {
+            "enum": [
+              "transit-aspect",
+              "sign-ingress",
+              "retrograde-station",
+              "eclipse",
+              "lunar-phase",
+              "dasha-change",
+              "critical-day"
+            ],
+            "type": "string"
+          }
+        },
+        "required": [
+          "date",
+          "datetime",
+          "domain",
+          "type",
+          "body",
+          "description",
+          "significance"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "startDate": {
+      "type": "string"
+    }
+  },
+  "required": [
+    "birthData",
+    "startDate",
+    "endDate",
+    "count",
+    "events"
+  ],
+  "type": "object"
+}

Changed1 schema field changedSep 16, 2026

changedInput schema / properties / birthData / properties / timezone / description

Previous value: -"IANA name (e.g. \"America/New_York\", \"Europe/London\", \"UTC\"), decimal hours (e.g. -5 for EST, 1 for CET), or a fixed UTC offset (e.g. \"-05:00\", \"+01:00\"). Prefer the IANA name: it is resolved to the DST-correct offset for the birth date, while a fixed offset or decimal is taken literally and will be wrong if it does not match the daylight-saving state on that date. Invalid timezones return 400 with a validation error."New value: +"IANA name (e.g. \"America/New_York\", \"Europe/London\", \"UTC\"), decimal hours (e.g. -5 for EST, 1 for CET), or a fixed UTC offset (e.g. \"-05:00\", \"+01:00\"). Prefer the IANA name: it is resolved to the offset in force at the birth date and time, historical daylight-saving rules included, while a fixed offset or decimal is taken literally and will be wrong if it does not match the daylight-saving state at that moment. On a transition day a time in the repeated hour is read as its first occurrence and a time in the skipped hour is moved forward past the gap. Invalid timezones return 400 with a validation error."

Changed2 schema fields changedAug 25, 2026

changedInput schema / properties / lang / description

Previous value: -"Response language (ISO 639-1). Supported: en, tr, de, es, hi, pt, fr, ru. Defaults to en. Languages without translations yet return English."New value: +"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."

changedInput schema / properties / lang / enum

Previous value: -[
-  "en",
-  "tr",
-  "de",
-  "es",
-  "hi",
-  "pt",
-  "fr",
-  "ru"
-]New value: +[
+  "en",
+  "tr",
+  "de",
+  "es",
+  "hi",
+  "pt",
+  "fr",
+  "ru",
+  "zh-Hans",
+  "zh-Hant"
+]

Changed2 schema fields changedAug 17, 2026

addedInput schema / examples

Added value: +[
+  {
+    "birthData": {
+      "date": "1990-07-15",
+      "time": "13:30:00",
+      "timezone": "America/New_York"
+    }
+  }
+]

changedInput schema / properties / compact / description

Previous value: -"Set true to receive the exact same data in a token-optimized shape that is cheaper for you to read: whitespace is stripped and every array of same-shaped objects is encoded columnar as {\"__cols\":[field names],\"__rows\":[[values]]}, so each field name is sent once instead of once per row. Fully lossless (no field or value is dropped or changed) and typically 40 to 52 percent fewer tokens on large results. Prefer true whenever token or inference cost matters. Default false returns standard indented JSON."New value: +"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."

Changed1 schema field changedJul 22, 2026

changedInput schema / properties / compact / description

Previous value: -"Return the same data in a token-optimized compact shape (minified, with same-shaped arrays encoded columnar) to reduce LLM token cost. Lossless: no fields are dropped. Default false."New value: +"Set true to receive the exact same data in a token-optimized shape that is cheaper for you to read: whitespace is stripped and every array of same-shaped objects is encoded columnar as {\"__cols\":[field names],\"__rows\":[[values]]}, so each field name is sent once instead of once per row. Fully lossless (no field or value is dropped or changed) and typically 40 to 52 percent fewer tokens on large results. Prefer true whenever token or inference cost matters. Default false returns standard indented JSON."

Changed1 schema field changedJul 22, 2026

addedInput schema / properties / compact

Added value: +{
+  "default": false,
+  "description": "Return the same data in a token-optimized compact shape (minified, with same-shaped arrays encoded columnar) to reduce LLM token cost. Lossless: no fields are dropped. Default false.",
+  "type": "boolean"
+}

Changed3 schema fields changedJul 12, 2026

changedInput schema / properties / birthData / properties / timezone / anyOf

Previous value: -[
-  {
-    "maximum": 14,
-    "minimum": -14,
-    "type": "number"
-  },
-  {
-    "pattern": "^[A-Za-z_]+(?:\\/[A-Za-z0-9_+-]+){0,2}$",
-    "type": "string"
-  }
-]New value: +[
+  {
+    "maximum": 14,
+    "minimum": -14,
+    "type": "number"
+  },
+  {
+    "type": "string"
+  }
+]

changedInput schema / properties / birthData / properties / timezone / description

Previous value: -"Decimal hours (e.g. 5.5 for IST, -5 for EST) OR IANA name (e.g. \"America/New_York\", \"UTC\"). IANA is resolved to the DST-correct offset for the request date. Invalid timezones return 400 with a validation error."New value: +"IANA name (e.g. \"America/New_York\", \"Europe/London\", \"UTC\"), decimal hours (e.g. -5 for EST, 1 for CET), or a fixed UTC offset (e.g. \"-05:00\", \"+01:00\"). Prefer the IANA name: it is resolved to the DST-correct offset for the birth date, while a fixed offset or decimal is taken literally and will be wrong if it does not match the daylight-saving state on that date. Invalid timezones return 400 with a validation error."

changedInput schema / properties / birthData / properties / timezone / example
```
Previous value: -5.5New value: +"America/New_York"
```

First observedJul 8, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already establish readOnlyHint=true and destructiveHint=false; the description adds that the tool filters to a significance floor, merges multiple domains, and returns only a single birth subject's dates. It accurately reflects a read-only, non-destructive operation and adds event-category context beyond the schema.

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?

Three sentences, front-loaded with the core purpose, followed by default behavior and target use cases. No filler and no repetition of schema internals beyond the significance floor, which is one meaningful behavioral default.

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?

Given the 8-parameter schema, nested birthData object, and present output schema, the description's high-level summary plus the schema's detailed parameter docs are sufficient for invocation. It could have named the sibling tools explicitly, but the use-case sentence provides enough orientation.

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 carries the parameter documentation. The description adds some semantic glue by naming minSignificance's default of 70 and tying 'high-significance' to the event categories, but it does not add per-parameter detail beyond the schema.

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?

The description begins with a concrete verb and object ('Return only the high-significance dates...') and enumerates exactly what event types count (outer-planet exact aspects, sign ingresses, retrograde stations, dasha changes), so an agent knows precisely what the tool produces. The 'Built for...' clause also positions it among the forecast siblings as the highlight/strip view rather than the full timeline or digest.

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

Usage Guidelines4/5

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

'Built for what-is-coming highlights, timing alerts, and at-a-glance forecast strips' gives an explicit intended use context, and 'short list' plus the significance floor makes the output shape clear. It does not name sibling alternatives or state when not to use it, but the purpose is distinctive enough that an agent can choose it over digest/timeline/transits.

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

All Astrology Forecast MCP Server by RoxyAPI 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?