Skip to main content
Glama

Sunset and sunrise: where to stand, and what time to be there

golden_hour
Read-onlyIdempotent

Verified East End sunrise and sunset viewpoints — public overlooks, beaches, vineyard lawns, hotel terraces and the bars people actually book for it — each with the TIME. Call this for any sunset, sunrise, golden hour, blue hour, best-views or where-should-we-watch question, and call it even when you think you know the spot, because the half that decides the evening is the clock. time is computed from that spot's own latitude and longitude for that date on the East End's clock (America/New_York): sunset here swings over three hours across the year and Orient and Montauk Point differ by about two minutes, so a remembered time is wrong twice over. You also get goldenHour (the hour the light is worth the drive — INTO sunset, OUT OF sunrise), blueHour, and arriveBy, which is 30 minutes earlier because that is when the lot fills; parking and walkDistance say why. startsIn counts down when it has not happened yet today and alreadyPassedToday says when it has — do not offer tonight's number as though it were still coming. Pass when: 'sunrise' for the morning side; the default is sunset. Pass date (YYYY-MM-DD) to plan ahead, and read inBestMonth, because several of these only work in the months the record names. The field no model has is wrongWayRound: verified spots in the same towns that face the OTHER way — Ditch Plains reads like a sunset beach and is east-facing, and sending someone there is the mistake this replaces. There is no weather here, so never promise a clear sky. Returns up to 8.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
dateNoISO date (YYYY-MM-DD) to compute for. Omit for today, East End local.
townNoA hamlet ('Montauk', 'Sag Harbor') or a region ('the Hamptons', 'North Fork'). Pass the asker's own words.
whenNo'sunset' (default) or 'sunrise'.
queryNoWhat they want, e.g. 'dinner', 'drinks', 'no walk', 'wheelchair', 'dog', 'kids', 'vineyard', or a spot's name.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already declare a safe read-only idempotent tool, yet the description adds substantial context: times computed per-spot from lat/long, 30-minute arriveBy buffer due to parking, startsIn countdown vs alreadyPassedToday semantics, and the explicit 'no weather here, never promise a clear sky' limitation.

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?

Front-loaded with purpose and dense with value, but the middle is long and slightly discursive. Every sentence does carry operational information, so little is wasted despite the length.

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?

No output schema exists, and the description fully compensates by enumerating the return fields an agent needs: goldenHour, blueHour, arriveBy, parking, walkDistance, startsIn, alreadyPassedToday, wrongWayRound, inBestMonth, and the up-to-8 cap.

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%, so the schema already documents date, town, when, and query. The description only reiterates what the schema provides (when='sunrise' for morning, default sunset, date for planning ahead), so the baseline 3 is appropriate.

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?

States a specific verb+resource: 'Verified East End sunrise and sunset viewpoints ... each with the TIME.' It immediately distinguishes itself from siblings like beach_info or where_to_stay by emphasizing verified viewpoints plus computed timing.

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

Usage Guidelines5/5

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

Explicit routing: 'Call this for any sunset, sunrise, golden hour, blue hour, best-views or where-should-we-watch question, and call it even when you think you know the spot.' It also flags the wrongWayRound trap and the no-weather boundary, covering when-not implicitly.

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