Hamptons Verified

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

golden_hour

Read-onlyIdempotent

Verified East End sunrise and sunset viewpoints, 31 in all: public overlooks, beaches, vineyard lawns, hotel terraces and bars, each with the time. time is computed from that spot's own latitude and longitude for the 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. Each row also carries goldenHour (the hour into sunset, or out of sunrise), blueHour, arriveBy (30 minutes earlier, when the lot fills), parking and walkDistance. startsIn counts down when it has not happened yet today; alreadyPassedToday is set when it has. when: 'sunrise' gives the morning side; the default is sunset. date (YYYY-MM-DD) computes for another day, and inBestMonth says whether that date falls in the months the record names. wrongWayRound lists verified spots in the same towns that face the other way (Ditch Plains is east-facing). The data holds no weather. Returns up to 8. townScope reports how the place argument was read; townScope.recognized: false means the name matched no East End place, the rows array is empty, and didYouMean lists near matches where any exist.

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

Input Schema

Name	Required	Description
`date`	No	ISO date (YYYY-MM-DD) to compute for. Omit for today, East End local.
`town`	No	A hamlet ('Montauk', 'Sag Harbor') or a region ('the Hamptons', 'North Fork'), in the asker's own words.
`when`	No	'sunset' (default) or 'sunrise'.
`query`	No	What to look for, e.g. 'dinner', 'drinks', 'no walk', 'wheelchair', 'dog', 'kids', 'vineyard', or a spot's name.

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedNov 3, 2026

changedInput schema / properties / query / description

Previous value: -"What they want, e.g. 'dinner', 'drinks', 'no walk', 'wheelchair', 'dog', 'kids', 'vineyard', or a spot's name."New value: +"What to look for, e.g. 'dinner', 'drinks', 'no walk', 'wheelchair', 'dog', 'kids', 'vineyard', or a spot's name."

changedInput schema / properties / town / description

Previous value: -"A hamlet ('Montauk', 'Sag Harbor') or a region ('the Hamptons', 'North Fork'). Pass the asker's own words."New value: +"A hamlet ('Montauk', 'Sag Harbor') or a region ('the Hamptons', 'North Fork'), in the asker's own words."

Changed1 schema field changedOct 26, 2026

changedInput schema / $schema

Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"

First observedAug 17, 2026

TDQS

A4.1/5.0

Behavior5/5

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

Annotations already establish the safe read-only profile, and the description adds substantial behavioral context: computed local times, return limit of 8, no weather data, empty rows on unrecognized towns, and `didYouMean` fallback behavior. It also explains edge cases like `startsIn`, `alreadyPassedToday`, and `wrongWayRound`.

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?

The description front-loads the purpose and packs necessary output-field details into a single dense paragraph. Most of the detail earns its place because there is no output schema, though ancillary facts like the three-hour seasonal swing and two-minute geographic difference are interesting rather than essential.

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?

Given the absence of an output schema, the description does a thorough job explaining return count, key output fields, timezone behavior, and failure modes such as unmatched towns. It gives an agent enough context to call and interpret the tool correctly.

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

Parameters4/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 all four parameters. The description adds meaningful interpretation for `town` by explaining `townScope.recognized` and `didYouMean`, and supplies context for `date` and `when`, though it mostly repeats the schema's parameter definitions and adds little for `query` beyond examples.

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 identifies the resource and scope: verified East End sunrise and sunset viewpoints, with computed times and supporting fields. It is easy to tell this is a dedicated golden-hour lookup rather than generic place search, but it does not name a sibling tool or use an explicit verb like 'find' or 'list'.

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

Usage Guidelines3/5

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

Usage is implied through parameter explanations such as `when: 'sunrise'` for the morning side and `date` for another day. However, there is no explicit guidance on when to choose this tool over siblings like `things_to_do`, `search_places`, or `beach_info`.

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

All Hamptons Verified 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.

Resources

Need Help?