AstroWay Platform

Stream Ingress

astroway_stream_ingress

Next planet sign-ingresses for N days.

[Group: Real-time Streaming] [Endpoint: POST /v1/stream/ingress] [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_ingress"
  }
}

Input Schema

Name	Required	Description
`days`	No
`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
`ingresses`	No
`transport`	No
`sseUpgrade`	No
`windowDays`	No
`nextEventAt`	No
`tickSeconds`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed17 schema fields changedNov 7, 2026

removedInput schema / properties / days / anyOf

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

addedInput schema / properties / days / type

Added value: +[
+  "number",
+  "null"
+]

removedOutput schema / properties / count / anyOf

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

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

changedOutput schema / properties / ingresses / anyOf

Previous value: -[
-  {
-    "items": {
-      "anyOf": [
-        {
-          "additionalProperties": {},
-          "properties": {
-            "at": {
-              "anyOf": [
-                {
-                  "type": "string"
-                },
-                {
-                  "type": "null"
-                }
-              ]
-            },
-            "longitude": {
-              "anyOf": [
-                {
-                  "type": "number"
-                },
-                {
-                  "type": "null"
-                }
-              ]
-            },
-            "planet": {
-              "anyOf": [
-                {
-                  "type": "string"
-                },
-                {
-                  "type": "null"
-                }
-              ]
-            },
-            "planetId": {
-              "anyOf": [
-                {
-                  "type": "number"
-                },
-                {
-                  "type": "null"
-                }
-              ]
-            },
-            "sign": {
-              "anyOf": [
-                {
-                  "type": "string"
-                },
-                {
-                  "type": "null"
-                }
-              ]
-            }
-          },
-          "type": "object"
-        },
-        {
-          "type": "null"
-        }
-      ]
-    },
-    "type": "array"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "items": {
+      "anyOf": [
+        {
+          "additionalProperties": {},
+          "properties": {
+            "at": {
+              "type": [
+                "string",
+                "null"
+              ]
+            },
+            "longitude": {
+              "type": [
+                "number",
+                "null"
+              ]
+            },
+            "planet": {
+              "type": [
+                "string",
+                "null"
+              ]
+            },
+            "planetId": {
+              "type": [
+                "number",
+                "null"
+              ]
+            },
+            "sign": {
+              "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 / transport / anyOf

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

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

removedOutput schema / properties / windowDays / anyOf

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

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

First observedOct 5, 2026

TDQS

B3.1/5.0

Behavior3/5

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

Annotations already declare openWorldHint=true and non-idempotent, non-destructive behavior. The description adds genuinely new context beyond those: the transport (POST /v1/stream/ingress) and a concrete cost (10 credits, Tier 1), which matters for a billed call. It stops short of explaining streaming semantics, whether results are bounded, or why readOnlyHint=false on what reads as a query.

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?

One functional sentence followed by three bracketed metadata lines; the payload sentence is front-loaded and there is no filler. The Group/Endpoint/Cost lines are terse and earn their place given the per-call credit charge, though the group tag adds little.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists, so return shape needn't be explained, but key invocation details are missing: which bodies count (Sun/Moon? all planets?), what the timezone/window anchor is, and what `days` defaults to when omitted (it is not required). For a billed, open-world streaming query among a dozen similar stream/webhook siblings, this leaves real gaps.

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 coverage is 67%: `fields` and `precision` are well documented in the schema, but `days` carries no description there, and the phrase "for N days" only weakly ties it to that parameter — no default, unit confirmation, or upper bound is given. Baseline 3 is appropriate since the schema does most of the work.

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?

"Next planet sign-ingresses for N days" names both the resource (planet sign ingresses) and the time horizon (N days), so an agent can tell it returns an upcoming-events list rather than current positions. It does not differentiate itself from near-name siblings such as astroway_stream_transit_alerts or astroway_webhooks_sign_ingress, but the core verb+resource is unambiguous.

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 gives no when-to-use guidance, no prerequisites, and no alternatives. With siblings like astroway_webhooks_sign_ingress (subscription-based) and astroway_stream_positions (current state), an agent is left to infer from names alone which one answers "when does a planet change sign?".

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

All AstroWay Platform tools Inspect

Try in Browser

Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?