Skip to main content
Glama

Prayer times and sun times

Sunrise, sunset and twilight times

sun_times
Read-onlyIdempotent

Sunrise, sunset, solar noon, day length, and civil, nautical and astronomical dawn and dusk for a town, city or coordinates on a date, in local time.

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": "sun_times"
  }
}

Input Schema

NameRequiredDescriptionDefault
dateNoYYYY-MM-DD; default today in the place's timezone.
placeNoTown or city name, optionally with country: "Riyadh", "Birmingham, UK", "القاهرة". Or use latitude/longitude.
countryNoOptional ISO 3166-1 alpha-2 code or country name to pick among same-named towns.
latitudeNo
timezoneNoIANA timezone for coordinates, e.g. "Europe/London". Default: from the nearest town.
longitudeNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/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 openWorldHint=false, so safety and repeatability are covered. The description's only real addition is that results are expressed 'in local time', which is genuinely useful output context, but nothing is said about unresolved places, invalid dates, or whether a timezone is required when using coordinates.

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?

A single front-loaded sentence with no filler; every listed quantity earns its place. The long comma-chained enumeration of twilight phases is dense to parse but not padded.

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

Completeness3/5

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

With no output schema, the enumeration of returned values does useful work, and all six parameters are optional so there is no required-input gap. Still missing for a location-dependent tool: how coordinate pairs are validated, what happens when a place name is ambiguous or unknown, and the unit/format of day length.

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%, so most parameters are already documented. The description adds the meaningful hint that a place name and coordinates are alternative ways to specify location, but it never states that latitude and longitude must be supplied together, how day length is expressed, or that timezone only matters for coordinate input.

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 enumerates exactly what is returned (sunrise, sunset, solar noon, day length, three twilight phases) and for what inputs (place or coordinates, on a date). This is far more specific than a restated title and lets an agent distinguish it from an astronomical/prayer-time style tool, though it never names a sibling to contrast with.

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 or when-not guidance, and no mention of the available alternatives such as prayer_times, whose dawn/dusk notions overlap conceptually with this tool's twilight values. The agent must infer selection criteria entirely from the output list.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources