Skip to main content
Glama

Astrology Forecast MCP Server by RoxyAPI

by com.roxyapi
OverviewDiscussionsAdmin

Cross-domain forecast timeline - Transits, ingresses, stations, dasha changes, critical days

post_forecast_timeline
Read-only

Build one time-ordered forecast for a single birth subject by merging upcoming events across three domains: western transit-to-natal aspects, sign ingresses, retrograde stations, eclipses, and new and full moons; biorhythm critical days; and vedic Vimshottari mahadasha, antardasha, and pratyantardasha boundaries. The window is clamped to 90 days and events are capped and scored by significance. Built for what-is-coming dashboards, daily and weekly forecast feeds, and timing tools.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
langNoResponse 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
compactNoSet 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.
domainsNoWhich forecast domains to include. Defaults to all three. Pass a subset to scope the timeline to one or two engines.
endDateNoLast day of the forecast window in YYYY-MM-DD format. Defaults to startDate plus 30 days. The window is clamped to a maximum of 90 days from startDate.
birthDataYesThe single birth subject this forecast is built for. One object only, never an array.
startDateNoFirst day of the forecast window in YYYY-MM-DD format. Defaults to today in UTC.
domainWeightsNoPer-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.
minSignificanceNoDrop events scoring below this significance threshold from 0 to 100. Defaults to 0, keeping all events.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
countYes
eventsYes
endDateYes
birthDataYes
startDateYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • 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"
+}
  2. Changed1 schema field changed
    • 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."
  3. Changed2 schema fields changed
    • 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"
+]
  4. Changed2 schema fields changed
    • 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."
  5. Changed1 schema field changed
    • 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."
  6. Changed1 schema field changed
    • 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"
+}
  7. Changed3 schema fields changed
    • 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"
  8. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds valuable behavioral constraints beyond the schema: the window is clamped to 90 days, events are capped and scored by significance, and the tool merges events across domains into one timeline. It does not detail the exact cap or scoring formula, but the schema's minSignificance/domainWeights parameters already hint at that mechanism.

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 with no filler. The first sentence states the core action and scope, the second adds the key constraints (90-day clamp, cap, scoring), and the third names the target use cases. Every sentence earns its place and the most important information is front-loaded.

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?

The tool has a rich output schema (not shown but present), 100% schema coverage, and read-only annotations, so the description does not need to explain return values or safety. It covers the merging behavior, window clamp, event cap/scoring, and intended use cases. A minor gap is not explicitly stating that domains defaults to all three, but the schema already documents that default.

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 already documents all 8 parameters thoroughly. The description adds the high-level merging and clamping behavior but does not add per-parameter meaning beyond what the schema provides. Baseline 3 is appropriate when the schema carries the full parameter documentation burden.

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 a specific verb ('Build') and a precise resource ('one time-ordered forecast for a single birth subject'), then enumerates the three merged domains (western transits/ingresses/stations/eclipses/lunations, biorhythm critical days, vedic dasha boundaries). This clearly distinguishes it from sibling forecast tools like post_forecast_transits (single-domain) or post_forecast_digest (likely a summary), and the title reinforces the cross-domain scope.

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?

The description states the intended use cases ('Built for what-is-coming dashboards, daily and weekly forecast feeds, and timing tools') and the domain-merging behavior, which implies when to choose this over single-domain siblings. It does not explicitly name alternatives or say 'use post_forecast_transits for western-only', but the cross-domain framing plus sibling names gives an agent enough context to route correctly.

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 toolsInspect
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