Sunvane Golden Hour

Find sun times

find_sun_times

Read-only

Use this when the user asks for a golden hour calculator, golden hour time, sunrise sunset times, sunset time today, what time is golden hour, blue hour, sunrise time, or twilight times for a city and local date. Returns local sunrise, sunset, solar noon, day length, twilight, light windows and sun azimuth. Limits: cities with population 50,000+ (plus Tromso), dates 1900–2100, flat sea-level horizon; Does not model weather or terrain.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "city": "<city>",
      "date": "<date>"
    },
    "name": "find_sun_times"
  }
}

Input Schema

Name	Required	Description
`city`	Yes	City name, for example New York. Cities with population 50,000+ are supported; the largest same-name match is used.
`date`	Yes	Local calendar date, YYYY-MM-DD, from 1900 to 2100; for example 2026-06-21.
`state`	No	Optional US state name or abbreviation, for example NY or New York.
`country`	No	Optional country name or two-letter code to narrow the match, for example US.

Output Schema

Name	Required	Description	Default
`blue`	No
`date`	No
`days`	No
`mode`	Yes
`civil`	No
`golden`	No
`period`	No
`sunset`	No
`values`	No
`changes`	No
`preview`	No
`request`	Yes
`sunrise`	No
`location`	Yes
`nautical`	No
`timeZone`	No
`dayLength`	No
`dayStatus`	No
`downloads`	No
`solarNoon`	No
`startDate`	No
`eventCount`	No
`definitions`	Yes
`limitations`	Yes
`astronomical`	No
`sunsetAzimuth`	No
`sunriseAzimuth`	No
`dayLengthSeconds`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 22, 2026

TDQS

A4.1/5.0

Behavior5/5

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

The Limits sentence adds real behavioral scope beyond the annotations: city population floor (50,000+, plus Tromso), date range 1900–2100, and a flat sea-level horizon with no weather or terrain modeling. That tells an agent precisely when results will be wrong or unavailable, which the readOnly/openWorld annotations do not.

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-loads the use-when triggers and puts limits last, where they belong. The trigger list is somewhat keyword-stuffed and repeats 'sunrise time' / 'sunset time' variants, but the density serves retrieval rather than padding.

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?

An output schema exists so return values need no elaboration, and the description still sketches the result shape plus hard coverage limits. For a two-required-parameter read-only lookup, nothing an agent needs to call it correctly is missing.

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 description coverage is 100%, so city, date, state and country are already fully documented with formats and examples. The description only restates the population and date bounds, adding no syntax or disambiguation guidance beyond the schema.

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?

States a specific resource and enumerates exactly what is returned (local sunrise, sunset, solar noon, day length, twilight, light windows, sun azimuth). It does not name or distinguish itself from the siblings compare_day_length and plan_golden_hour_shoot, both of which overlap with its 'golden hour' trigger phrases.

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 first sentence is an explicit use-when list covering golden hour, sunrise/sunset, blue hour and twilight queries, which gives an agent clear selection context. It offers no exclusions and never says when a sibling tool is the better choice.

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

All Sunvane Golden Hour 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?