AstroWay Platform

Stream Sunrise/Sunset

astroway_stream_sunrise_sunset

Today + tomorrow sun events.

[Group: Real-time Streaming] [Endpoint: POST /v1/stream/sunrise-sunset] [Required: latitude, longitude] [Cost: 10 credits (Tier 1)]

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "latitude": "<latitude>",
      "longitude": "<longitude>"
    },
    "name": "astroway_stream_sunrise_sunset"
  }
}

Input Schema

Name	Required	Description
`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.
`latitude`	Yes
`longitude`	Yes
`precision`	No	Compact mode: round fractional numbers to this many decimals. Longitudes carry 14 by default; 2 is finer than any chart is drawn.
`timezoneOffset`	No	Hours from UTC at the given moment, not minutes. Fractional zones are hours too: 5.5 for India, 5.75 for Nepal, -3.5 for Newfoundland. Defaults to 0, meaning UTC.

Output Schema

Name	Required	Description	Default
`today`	No
`pricing`	No
`tomorrow`	No
`timestamp`	No
`transport`	No
`sseUpgrade`	No
`nextEventAt`	No
`tickSeconds`	No
`nextEventKind`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed20 schema fields changedNov 7, 2026

removedInput schema / properties / latitude / anyOf

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

addedInput schema / properties / latitude / type
```
Added value: +[
+  "number",
+  "null"
+]
```

removedInput schema / properties / longitude / anyOf

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

addedInput schema / properties / longitude / type
```
Added value: +[
+  "number",
+  "null"
+]
```

removedOutput schema / properties / nextEventAt / anyOf

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

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

removedOutput schema / properties / nextEventKind / anyOf

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

addedOutput schema / properties / nextEventKind / 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"
+]
```

changedOutput schema / properties / today / anyOf

Previous value: -[
-  {
-    "additionalProperties": {},
-    "properties": {
-      "date": {
-        "anyOf": [
-          {
-            "type": "string"
-          },
-          {
-            "type": "null"
-          }
-        ]
-      },
-      "polarState": {
-        "anyOf": [
-          {
-            "type": "string"
-          },
-          {
-            "type": "null"
-          }
-        ]
-      },
-      "sunrise": {
-        "anyOf": [
-          {
-            "type": "string"
-          },
-          {
-            "type": "null"
-          }
-        ]
-      },
-      "sunset": {
-        "anyOf": [
-          {
-            "type": "string"
-          },
-          {
-            "type": "null"
-          }
-        ]
-      },
-      "warning": {
-        "anyOf": [
-          {},
-          {
-            "type": "null"
-          }
-        ]
-      }
-    },
-    "type": "object"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "additionalProperties": {},
+    "properties": {
+      "date": {
+        "type": [
+          "string",
+          "null"
+        ]
+      },
+      "polarState": {
+        "type": [
+          "string",
+          "null"
+        ]
+      },
+      "sunrise": {
+        "type": [
+          "string",
+          "null"
+        ]
+      },
+      "sunset": {
+        "type": [
+          "string",
+          "null"
+        ]
+      },
+      "warning": {
+        "anyOf": [
+          {},
+          {
+            "type": "null"
+          }
+        ]
+      }
+    },
+    "type": "object"
+  },
+  {
+    "type": "null"
+  }
+]

changedOutput schema / properties / tomorrow / anyOf

Previous value: -[
-  {
-    "additionalProperties": {},
-    "properties": {
-      "date": {
-        "anyOf": [
-          {
-            "type": "string"
-          },
-          {
-            "type": "null"
-          }
-        ]
-      },
-      "polarState": {
-        "anyOf": [
-          {
-            "type": "string"
-          },
-          {
-            "type": "null"
-          }
-        ]
-      },
-      "sunrise": {
-        "anyOf": [
-          {
-            "type": "string"
-          },
-          {
-            "type": "null"
-          }
-        ]
-      },
-      "sunset": {
-        "anyOf": [
-          {
-            "type": "string"
-          },
-          {
-            "type": "null"
-          }
-        ]
-      }
-    },
-    "type": "object"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "additionalProperties": {},
+    "properties": {
+      "date": {
+        "type": [
+          "string",
+          "null"
+        ]
+      },
+      "polarState": {
+        "type": [
+          "string",
+          "null"
+        ]
+      },
+      "sunrise": {
+        "type": [
+          "string",
+          "null"
+        ]
+      },
+      "sunset": {
+        "type": [
+          "string",
+          "null"
+        ]
+      }
+    },
+    "type": "object"
+  },
+  {
+    "type": "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

C2.8/5.0

Behavior3/5

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

The description adds genuinely useful behavioral context the annotations do not carry: the concrete endpoint (POST /v1/stream/sunrise-sunset) and a stated cost of 10 credits, Tier 1, which matters for a costly call. What it omits is the actual meaning of "stream" here — whether this opens a persistent/SSE subscription versus returning a single two-day payload — especially given openWorldHint=true, idempotentHint=false and destructiveHint=false that the description never reconciles.

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?

It is a compact, well-structured tag block with the scope statement first and metadata following, and there is no filler prose. The tradeoff is that the brevity veers into under-specification rather than tight writing.

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?

For a 5-parameter, credit-consuming streaming endpoint in a family of near-identical stream tools, the definition leaves the core questions unanswered: what triggers a response, whether it is a subscription or a single call, and what events besides sunrise/sunset are included. An output schema exists so return values need no explanation, but the interaction and cost model are otherwise too thin.

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 60%: fields, precision, and timezoneOffset are already documented in-schema, so the description's '[Required: latitude, longitude]' merely repeats the required array with no added format or semantics. The 14-decimal longitude precision claim and timezone behavior, the parameters most likely to be misused, are left entirely to the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

"Today + tomorrow sun events" paired with the name conveys that this returns sunrise/sunset-related events for a two-day window, which is clearer than a bare restatement. However, it never actually says "sunrise and sunset" in the description body, and it does nothing to separate it from the many other stream_* siblings such as astroway_stream_lunar_phase or astroway_stream_positions.

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?

There is no when-to-use guidance: nothing says when to pick this over the webhook equivalents (astroway_webhooks_*), the generic stream tools, or a one-off chart calculation. The only routing-like information is the machine tag '[Group: Real-time Streaming]', which implies a category but not a selection rule or exclusion.

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?