Astrology Forecast MCP Server by RoxyAPI

Forecast digest - Pre-summarized next 24h, 7d, 30d, and 90d rollups

post_forecast_digest

Read-only

Roll the cross-domain forecast for a single birth subject into four pre-summarized windows: the next 24 hours, 7 days, 30 days, and 90 days from the start date. Each window returns its event count, a per-domain count breakdown, a per-type count breakdown, and the top highest-significance events. Built for a glanceable what-is-coming strip so a caller can render the upcoming highlights without scanning the full event list.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`top`	No	Number of highest-significance events to surface per window. Defaults to 3, capped at 20.
`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 include before rolling up the windows. Defaults to all three.
`birthData`	Yes	The single birth subject this digest is built for. One object only, never an array.
`startDate`	No	Start anchor for every window in YYYY-MM-DD format. The next 24h, 7d, 30d, and 90d windows are measured forward from this date at 00:00:00 UTC. 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	Drop events scoring below this significance threshold from 0 to 100 before the rollup. Defaults to 0.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`endDate`	Yes
`windows`	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"
+    },
+    "endDate": {
+      "type": "string"
+    },
+    "startDate": {
+      "type": "string"
+    },
+    "windows": {
+      "items": {
+        "properties": {
+          "byDomain": {
+            "properties": {
+              "biorhythm": {
+                "type": "number"
+              },
+              "vedic": {
+                "type": "number"
+              },
+              "western": {
+                "type": "number"
+              }
+            },
+            "type": "object"
+          },
+          "byType": {
+            "properties": {
+              "critical-day": {
+                "type": "number"
+              },
+              "dasha-change": {
+                "type": "number"
+              },
+              "eclipse": {
+                "type": "number"
+              },
+              "lunar-phase": {
+                "type": "number"
+              },
+              "retrograde-station": {
+                "type": "number"
+              },
+              "sign-ingress": {
+                "type": "number"
+              },
+              "transit-aspect": {
+                "type": "number"
+              }
+            },
+            "type": "object"
+          },
+          "count": {
+            "type": "number"
+          },
+          "days": {
+            "type": "number"
+          },
+          "from": {
+            "type": "string"
+          },
+          "to": {
+            "type": "string"
+          },
+          "top": {
+            "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"
+          }
+        },
+        "required": [
+          "days",
+          "from",
+          "to",
+          "count",
+          "byDomain",
+          "byType",
+          "top"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    }
+  },
+  "required": [
+    "birthData",
+    "startDate",
+    "endDate",
+    "windows"
+  ],
+  "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.3/5.0

Behavior4/5

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

The annotations already declare readOnlyHint=true and destructiveHint=false, so an agent knows this is a safe read operation. The description adds the behavioral nuance that the result is pre-aggregated into four windows with per-domain and per-type counts, plus top events, which is useful context beyond the safety flags. It does not discuss error cases or rate limits, but for a read-only digest with a rich schema and output schema, the added context is sufficient; no contradiction with annotations.

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?

The description is three sentences: the core verb+resource and window structure, then the output contents, then the use case. Each sentence is information-dense, the purpose is front-loaded, and there is no filler or repetition of schema fields. This is an exemplary structure.

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?

Despite having 8 parameters, one required and nested, plus an output schema, the description gives a complete mental model: the single birth subject, the four windows anchored at the start date, the breakdown dimensions, and the intended glanceable use. Since an output schema exists, it need not spell out return values; the description covers the conceptual and usage context needed to invoke it correctly.

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 every parameter, including nested fields like timezone and domainWeights, has a detailed schema description. The tool description itself only refers to 'top highest-significance events' and the window anchor, which mirrors schema text rather than adding new parameter semantics. Baseline 3 is correct.

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 opens with the specific verb 'Roll' and identifies both the resource ('the cross-domain forecast for a single birth subject') and the exact output ('four pre-summarized windows... event count, per-domain count breakdown, per-type count breakdown, and the top highest-significance events'). It distinguishes the digest from the sibling timeline/transits tools by emphasizing the pre-summarized, glanceable nature. This is a clear, differentiated purpose.

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?

It states the intended use case: 'Built for a glanceable what-is-coming strip so a caller can render the upcoming highlights without scanning the full event list.' This gives clear context for when to select it. It does not, however, explicitly name alternatives or state when not to use it (e.g., 'for the full event list, use post_forecast_timeline'), so it stops short of the explicit when/when-not guidance that would earn a 5.

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?