Sunvane Golden Hour

Plan golden hour shoot

plan_golden_hour_shoot

Read-only

Use this when the user wants photography golden hour shoot windows for a city and a date range, with an ICS calendar file and CSV table. Choose morning, evening or both. Limits: 1–31 days, cities with population 50,000+ (plus Tromso), years 1900–2100, flat sea-level horizon; missing polar windows are reported and calendar events are only included for existing windows. Does not access or change a calendar.

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>",
      "start_date": "<start_date>",
      "days": "<days>",
      "period": "<period>"
    },
    "name": "plan_golden_hour_shoot"
  }
}

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.
`days`	Yes	Number of consecutive days, 1 to 31, for example 7.
`state`	No	Optional US state name or abbreviation, for example NY or New York.
`period`	Yes	Light windows to include, for example evening. A continuous window includes both periods.
`country`	No	Optional country name or two-letter code to narrow the match, for example US.
`start_date`	Yes	First local date in YYYY-MM-DD, for example 2026-10-12.

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.7/5.0

Behavior5/5

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

Beyond the readOnly/non-destructive annotations, the description discloses concrete operating limits (1–31 days, 50,000+ population cities plus Tromso, years 1900–2100, flat sea-level horizon) and edge-case behavior: missing polar windows are reported while calendar events are only emitted for windows that exist. That's exactly the kind of context annotations can't carry.

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?

A single dense paragraph front-loads the trigger, then packs outputs, period choice, machine-readable limits, and an explicit non-behavior into consecutive clauses with no filler. Every sentence carries distinct information.

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?

With an output schema present, the description needn't explain return values, and it instead spends its budget on the operational limits and edge-case semantics an agent needs to call this correctly. Nothing material for correct invocation is missing.

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 baseline is 3, but the description adds cross-parameter constraints: the 1–31 day cap, the population threshold that qualifies a city match, and the morning/evening/both choice replicated for period. These reinforce rather than duplicate the per-field schema text.

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 definition states a specific verb and resource ('photography golden hour shoot windows for a city and a date range'), plus the two deliverable formats (ICS and CSV), making it clearly distinct from the sibling tools compare_day_length and find_sun_times. An agent can tell what it returns without opening the schema.

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 opening 'Use this when the user wants...' sentence gives a clear trigger condition, and the closing 'Does not access or change a calendar' rules out a plausible misreading. It stops short of naming a sibling tool or stating when to prefer an alternative, so it's a 4 rather than a 5.

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?