AstroWay Astrology API (full catalogue)

Stream Eclipse Incoming

astroway_stream_eclipse_incoming

Countdown to next 5 eclipses.

[Group: Real-time Streaming] [Endpoint: POST /v1/stream/eclipse-incoming] [Cost: 10 credits (Tier 1)]

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "astroway_stream_eclipse_incoming"
  }
}

Input Schema

Name	Required	Description	Default
`fields`	No	Compact mode: comma-separated dotted paths to keep, relative to `data`, e.g. "planets.name,planets.longitude,houses.cusp". Omit for the whole response.
`precision`	No	Compact mode: round fractional numbers to this many decimals. Longitudes carry 14 by default; 2 is finer than any chart is drawn.

Output Schema

Name	Required	Description	Default
`count`	No
`pricing`	No
`eclipses`	No
`timestamp`	No
`transport`	No
`sseUpgrade`	No
`nextEventAt`	No
`tickSeconds`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed15 schema fields changedNov 7, 2026

removedOutput schema / properties / count / anyOf

Removed value: -[
-  {
-    "type": "number"
-  },
-  {
-    "type": "null"
-  }
-]

addedOutput schema / properties / count / type
```
Added value: +[
+  "number",
+  "null"
+]
```

changedOutput schema / properties / eclipses / anyOf

Previous value: -[
-  {
-    "items": {
-      "anyOf": [
-        {
-          "additionalProperties": {},
-          "properties": {
-            "beginAt": {
-              "anyOf": [
-                {
-                  "type": "string"
-                },
-                {
-                  "type": "null"
-                }
-              ]
-            },
-            "daysUntil": {
-              "anyOf": [
-                {
-                  "type": "number"
-                },
-                {
-                  "type": "null"
-                }
-              ]
-            },
-            "endAt": {
-              "anyOf": [
-                {
-                  "type": "string"
-                },
-                {
-                  "type": "null"
-                }
-              ]
-            },
-            "hoursUntil": {
-              "anyOf": [
-                {
-                  "type": "number"
-                },
-                {
-                  "type": "null"
-                }
-              ]
-            },
-            "kind": {
-              "anyOf": [
-                {
-                  "type": "string"
-                },
-                {
-                  "type": "null"
-                }
-              ]
-            },
-            "longitude": {
-              "anyOf": [
-                {
-                  "type": "number"
-                },
-                {
-                  "type": "null"
-                }
-              ]
-            },
-            "maxAt": {
-              "anyOf": [
-                {
-                  "type": "string"
-                },
-                {
-                  "type": "null"
-                }
-              ]
-            },
-            "sign": {
-              "anyOf": [
-                {
-                  "type": "string"
-                },
-                {
-                  "type": "null"
-                }
-              ]
-            },
-            "type": {
-              "anyOf": [
-                {
-                  "type": "string"
-                },
-                {
-                  "type": "null"
-                }
-              ]
-            }
-          },
-          "type": "object"
-        },
-        {
-          "type": "null"
-        }
-      ]
-    },
-    "type": "array"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "items": {
+      "anyOf": [
+        {
+          "additionalProperties": {},
+          "properties": {
+            "beginAt": {
+              "type": [
+                "string",
+                "null"
+              ]
+            },
+            "daysUntil": {
+              "type": [
+                "number",
+                "null"
+              ]
+            },
+            "endAt": {
+              "type": [
+                "string",
+                "null"
+              ]
+            },
+            "hoursUntil": {
+              "type": [
+                "number",
+                "null"
+              ]
+            },
+            "kind": {
+              "type": [
+                "string",
+                "null"
+              ]
+            },
+            "longitude": {
+              "type": [
+                "number",
+                "null"
+              ]
+            },
+            "maxAt": {
+              "type": [
+                "string",
+                "null"
+              ]
+            },
+            "sign": {
+              "type": [
+                "string",
+                "null"
+              ]
+            },
+            "type": {
+              "type": [
+                "string",
+                "null"
+              ]
+            }
+          },
+          "type": "object"
+        },
+        {
+          "type": "null"
+        }
+      ]
+    },
+    "type": "array"
+  },
+  {
+    "type": "null"
+  }
+]

removedOutput schema / properties / nextEventAt / anyOf

Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]

addedOutput schema / properties / nextEventAt / type
```
Added value: +[
+  "string",
+  "null"
+]
```

removedOutput schema / properties / pricing / anyOf

Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]

addedOutput schema / properties / pricing / type
```
Added value: +[
+  "string",
+  "null"
+]
```

removedOutput schema / properties / sseUpgrade / anyOf

Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]

addedOutput schema / properties / sseUpgrade / type
```
Added value: +[
+  "string",
+  "null"
+]
```

removedOutput schema / properties / tickSeconds / anyOf

Removed value: -[
-  {
-    "type": "number"
-  },
-  {
-    "type": "null"
-  }
-]

addedOutput schema / properties / tickSeconds / type
```
Added value: +[
+  "number",
+  "null"
+]
```

removedOutput schema / properties / timestamp / anyOf

Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]

addedOutput schema / properties / timestamp / type
```
Added value: +[
+  "string",
+  "null"
+]
```

removedOutput schema / properties / transport / anyOf

Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]

addedOutput schema / properties / transport / type
```
Added value: +[
+  "string",
+  "null"
+]
```

First observedOct 5, 2026

TDQS

B3.2/5.0

Behavior3/5

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

The description adds genuinely useful context beyond the annotations: the 10-credit Tier 1 cost and the POST endpoint. However, it does not clarify whether this returns a single snapshot of five eclipses or an ongoing stream of countdown updates, which is the key behavioral question for a tool named "stream". There is mild tension between the read-like "countdown" framing and readOnlyHint=false, though POST-based streaming plausibly accounts for it, so this is not a true contradiction.

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 prose is a single front-loaded sentence with zero waste, and the bracketed group/endpoint/cost lines are compact and scannable. The cost line in particular earns its place, though the group and endpoint tags are somewhat boilerplate.

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?

With an output schema present, the description need not explain return values, and the cost disclosure is a helpful addition. Still, for a zero-required-parameter tool whose name promises streaming, the definition never says whether the call is one-shot or subscription-like, nor what time horizon "incoming" covers, leaving a meaningful gap for 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%, with both `fields` and `precision` thoroughly documented in the schema, including examples and sensible ranges. The description adds nothing about these parameters, which is acceptable given the schema already carries the meaning, but it also does not say how they interact with the eclipse countdown payload.

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 phrase "Countdown to next 5 eclipses" gives a concrete resource (upcoming eclipses) and an implied operation (countdown/timing retrieval), which is enough for an agent to distinguish it from astroway_stream_eclipse_totality or astroway_webhooks_eclipse_alert. It never explicitly states the contrast with those siblings, so differentiation depends on the names alone.

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

Usage Guidelines2/5

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

The description contains no when-to-use guidance, no exclusions, and no pointer to the near-duplicate siblings such as astroway_stream_eclipse_totality or astroway_webhooks_eclipse_alert. Only the bracketed group label hints that this belongs to a real-time streaming family; the choice between streaming and webhook variants is left entirely to inference.

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

All AstroWay Astrology API (full catalogue) 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?