sunrisesunset

Get Times Date

get_times_date

Read-onlyIdempotent

Get sunrise, sunset, dawn, dusk, solar noon, and golden hour times for a specific date at a location.

Input Schema

TableJSON Schema

Name	Required	Description
`lat`	Yes	Latitude of the location (e.g., 40.7128)
`lng`	Yes	Longitude of the location (e.g., -74.0060)
`date`	Yes	Date in YYYY-MM-DD format (e.g., "2024-06-21")

Output Schema

TableJSON Schema

Name	Required	Description
`lat`	Yes	Latitude of the location
`lng`	Yes	Longitude of the location
`date`	Yes	Date in YYYY-MM-DD format
`dawn`	Yes	Dawn time
`dusk`	Yes	Dusk time
`sunset`	Yes	Sunset time
`sunrise`	Yes	Sunrise time
`timezone`	Yes	Timezone identifier
`day_length`	Yes	Duration of daylight
`last_light`	Yes	Last light time
`solar_noon`	Yes	Solar noon time
`utc_offset`	Yes	UTC offset in hours
`first_light`	Yes	First light time
`golden_hour`	Yes	Golden hour time

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

Changed1 schema field changedMay 8, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "date": {
+      "description": "Date in YYYY-MM-DD format",
+      "type": "string"
+    },
+    "dawn": {
+      "description": "Dawn time",
+      "type": "string"
+    },
+    "day_length": {
+      "description": "Duration of daylight",
+      "type": "string"
+    },
+    "dusk": {
+      "description": "Dusk time",
+      "type": "string"
+    },
+    "first_light": {
+      "description": "First light time",
+      "type": "string"
+    },
+    "golden_hour": {
+      "description": "Golden hour time",
+      "type": "string"
+    },
+    "last_light": {
+      "description": "Last light time",
+      "type": "string"
+    },
+    "lat": {
+      "description": "Latitude of the location",
+      "type": "number"
+    },
+    "lng": {
+      "description": "Longitude of the location",
+      "type": "number"
+    },
+    "solar_noon": {
+      "description": "Solar noon time",
+      "type": "string"
+    },
+    "sunrise": {
+      "description": "Sunrise time",
+      "type": "string"
+    },
+    "sunset": {
+      "description": "Sunset time",
+      "type": "string"
+    },
+    "timezone": {
+      "description": "Timezone identifier",
+      "type": "string"
+    },
+    "utc_offset": {
+      "description": "UTC offset in hours",
+      "type": "number"
+    }
+  },
+  "required": [
+    "lat",
+    "lng",
+    "date",
+    "sunrise",
+    "sunset",
+    "first_light",
+    "last_light",
+    "dawn",
+    "dusk",
+    "solar_noon",
+    "golden_hour",
+    "day_length",
+    "timezone",
+    "utc_offset"
+  ],
+  "type": "object"
+}

Changed1 schema field changedMay 6, 2026

addedInput schema / examples

Added value: +[
+  {
+    "date": "2024-06-21",
+    "lat": 40.7128,
+    "lng": -74.006
+  },
+  {
+    "date": "2024-12-21",
+    "lat": 35.6762,
+    "lng": 139.6503
+  }
+]

First observedApr 14, 2026

TDQS

B3.4/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is established. The description adds context about the specific time values returned, but does not disclose other behavioral details like timezone handling or error conditions.

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?

The description is a single, focused sentence that lists the key outputs and the query parameters. It is appropriately concise with no filler.

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?

For a simple read-only lookup with an output schema and fully described parameters, the description covers the core purpose. It could be slightly more complete by addressing sibling differentiation or timezone assumptions, but it is sufficient for common use.

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 100% and each parameter (lat, lng, date) has a clear description. The tool description mostly reiterates the schema's semantic scope without adding new parameter-level details.

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 states the tool's verb and resource: it gets sunrise, sunset, dawn, dusk, solar noon, and golden hour times for a specific date and location. It is specific but does not explicitly differentiate from the sibling tool 'get_times'.

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 guidance on when to use this tool versus alternatives. It does not mention situations where get_times would be more appropriate or any exclusions.

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

All sunrisesunset tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.