Met No

Sunrise

sunrise

Read-onlyIdempotent

Sunrise / sunset / moon events for a date.

Input Schema

TableJSON Schema

Name	Required	Description
`lat`	Yes
`lon`	Yes
`date`	No	YYYY-MM-DD (default today UTC).
`offset`	No	UTC offset, e.g. "+01:00" (default "+00:00").

Output Schema

TableJSON Schema

Name	Required	Description	Default
`type`	No
`when`	No
`geometry`	No
`copyright`	No
`licenseURL`	No
`properties`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed8 schema fields changedOct 4, 2026

addedOutput schema / properties / copyright
```
Added value: +{
+  "type": "string"
+}
```

addedOutput schema / properties / geometry

Added value: +{
+  "properties": {
+    "coordinates": {
+      "items": {
+        "type": "number"
+      },
+      "type": "array"
+    },
+    "type": {
+      "type": "string"
+    }
+  },
+  "type": "object"
+}

addedOutput schema / properties / licenseURL
```
Added value: +{
+  "type": "string"
+}
```

removedOutput schema / properties / location

Removed value: -{
-  "properties": {
-    "height": {
-      "description": "Elevation in meters",
-      "type": "number"
-    },
-    "latitude": {
-      "type": "number"
-    },
-    "longitude": {
-      "type": "number"
-    }
-  },
-  "type": "object"
-}

addedOutput schema / properties / properties

Added value: +{
+  "properties": {
+    "body": {
+      "type": "string"
+    },
+    "solarmidnight": {
+      "properties": {
+        "disc_centre_elevation": {
+          "type": "number"
+        },
+        "time": {
+          "type": "string"
+        },
+        "visible": {
+          "type": "boolean"
+        }
+      },
+      "type": "object"
+    },
+    "solarnoon": {
+      "properties": {
+        "disc_centre_elevation": {
+          "type": "number"
+        },
+        "time": {
+          "type": "string"
+        },
+        "visible": {
+          "type": "boolean"
+        }
+      },
+      "type": "object"
+    },
+    "sunrise": {
+      "properties": {
+        "azimuth": {
+          "type": "number"
+        },
+        "time": {
+          "type": "string"
+        }
+      },
+      "type": "object"
+    },
+    "sunset": {
+      "properties": {
+        "azimuth": {
+          "type": "number"
+        },
+        "time": {
+          "type": "string"
+        }
+      },
+      "type": "object"
+    }
+  },
+  "type": "object"
+}

removedOutput schema / properties / time

Removed value: -{
-  "items": {
-    "properties": {
-      "date": {
-        "description": "Date in YYYY-MM-DD format",
-        "type": "string"
-      },
-      "high_moon": {
-        "description": "ISO 8601 timestamp",
-        "type": "string"
-      },
-      "low_moon": {
-        "description": "ISO 8601 timestamp",
-        "type": "string"
-      },
-      "moon_phase": {
-        "description": "Moon phase illumination fraction",
-        "type": "number"
-      },
-      "moonrise": {
-        "description": "ISO 8601 timestamp",
-        "type": "string"
-      },
-      "moonset": {
-        "description": "ISO 8601 timestamp",
-        "type": "string"
-      },
-      "sunrise": {
-        "description": "ISO 8601 timestamp",
-        "type": "string"
-      },
-      "sunset": {
-        "description": "ISO 8601 timestamp",
-        "type": "string"
-      }
-    },
-    "type": "object"
-  },
-  "type": "array"
-}

addedOutput schema / properties / type
```
Added value: +{
+  "type": "string"
+}
```

addedOutput schema / properties / when

Added value: +{
+  "properties": {
+    "interval": {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    }
+  },
+  "type": "object"
+}

Changed2 schema fields changedMay 22, 2026

addedInput schema / examples

Added value: +[
+  {
+    "lat": 59.9139,
+    "lon": 10.7522
+  },
+  {
+    "date": "2025-06-21",
+    "lat": 60.3913,
+    "lon": 5.3221,
+    "offset": "+02:00"
+  }
+]

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "location": {
+      "properties": {
+        "height": {
+          "description": "Elevation in meters",
+          "type": "number"
+        },
+        "latitude": {
+          "type": "number"
+        },
+        "longitude": {
+          "type": "number"
+        }
+      },
+      "type": "object"
+    },
+    "time": {
+      "items": {
+        "properties": {
+          "date": {
+            "description": "Date in YYYY-MM-DD format",
+            "type": "string"
+          },
+          "high_moon": {
+            "description": "ISO 8601 timestamp",
+            "type": "string"
+          },
+          "low_moon": {
+            "description": "ISO 8601 timestamp",
+            "type": "string"
+          },
+          "moon_phase": {
+            "description": "Moon phase illumination fraction",
+            "type": "number"
+          },
+          "moonrise": {
+            "description": "ISO 8601 timestamp",
+            "type": "string"
+          },
+          "moonset": {
+            "description": "ISO 8601 timestamp",
+            "type": "string"
+          },
+          "sunrise": {
+            "description": "ISO 8601 timestamp",
+            "type": "string"
+          },
+          "sunset": {
+            "description": "ISO 8601 timestamp",
+            "type": "string"
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    }
+  },
+  "type": "object"
+}

First observedMay 14, 2026

TDQS

C2.6/5.0

Behavior2/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint, and destructiveHint=false, covering the safety and mutability profile. The description adds no further behavioral context such as coordinate system expectations, timezone handling, or rate limits, so it provides no additional transparency beyond the annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, short fragment with no wasted words. However, it is under-specified rather than optimally structured—it lacks a verb and does not front-load required inputs—so it is minimal but not exemplary in structure.

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?

Given the tool requires latitude and longitude, the description never states that these are geographic coordinates or that they are mandatory. Output schema covers return values and annotations cover safety, but the description leaves input expectations for the required parameters unaddressed, making it incomplete for correct invocation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 50%: lat and lon are required but have no schema descriptions, and the description does not explain them either. The description mentions 'a date' but does not clarify date or offset semantics beyond what the schema already provides, so it fails to compensate for the undocumented required parameters.

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 description clearly names the astronomical events (sunrise, sunset, moon) and the temporal scope (a date), which is specific enough to identify the tool's purpose. It lacks a verb and does not explicitly differentiate from siblings, but no sibling covers the same domain, so an agent can still distinguish it.

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 provides no guidance on when to use this tool versus alternatives. It does not mention any conditions, prerequisites, or related tools, leaving the agent to infer usage entirely from the tool name and schema.

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

All Met No 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.