sunrisesunset

Get Times

get_times

Read-onlyIdempotent

Get today's sunrise, sunset, dawn, dusk, solar noon, golden hour, and day length for a given latitude and longitude. Returns all times in the location's local timezone.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`lat`	Yes	Latitude of the location (e.g., 40.7128)
`lng`	Yes	Longitude of the location (e.g., -74.0060)

Output Schema

TableJSON Schema

Name	Required	Description
`lat`	Yes	Latitude of the location
`lng`	Yes	Longitude of the location
`date`	Yes	Date string (literal 'today')
`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 string (literal 'today')",
+      "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: +[
+  {
+    "lat": 40.7128,
+    "lng": -74.006
+  },
+  {
+    "lat": 51.5074,
+    "lng": -0.1278
+  }
+]

First observedApr 14, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint false, so the safety profile is covered. The description adds value by specifying the output includes all listed times and that they are in the location's local timezone, which is a useful behavioral detail beyond what annotations provide.

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, well-structured sentence that immediately lists the outputs and the input requirement. Every word contributes to understanding, with no fluff or repetition. It is concise and front-loaded with the core functionality.

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

Completeness5/5

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

The tool is simple with two fully described parameters and an output schema, so the description does not need to explain return values. The description covers the essential context: what data is returned, for what location, and in what timezone. Combined with the annotations and schema, it is fully complete for an agent to select and invoke correctly.

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?

The input schema has 100% coverage for the two parameters (lat and lng) with descriptions and examples. The description only repeats 'given latitude and longitude' without adding new meaning or clarifying format beyond the schema, so the baseline score of 3 applies.

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

Purpose5/5

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

The description clearly states the tool 'Get today's sunrise, sunset, dawn, dusk, solar noon, golden hour, and day length for a given latitude and longitude.' This is a specific verb (Get) with a specific resource (times for a location), and the inclusion of 'today's' differentiates it from the sibling tool get_times_date, which likely handles other dates.

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

Usage Guidelines4/5

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

The description provides clear context: it is for getting today's times at a specific latitude/longitude, and returns local timezone times. However, it does not explicitly mention when not to use this tool or suggest alternatives like get_times_date for other dates. Thus, it has clear context but no exclusions or alternative references.

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.