Daylight Hours Skill

Overview

Returns detailed information including day of year, sunrise/sunset times, and formatted daylight duration, perfect for solar energy, agriculture, and travel applications.

Live Test Daylight Hours Skill Skill →

The tool

Once your client is connected to the VerveKit server, this appears in its tool list as DaylightHoursSkill. It is read-only and open-world — it fetches and never mutates anything on your side — so most clients call it without asking you to confirm.

Tool call

{
  "name": "DaylightHoursSkill",
  "arguments": {
    "latitude": "40.7128",
    "longitude": "-74.006"
  }
}

You do not name the tool yourself; the model picks it. Asking about 40.7128 in the terms this skill covers is enough for it to reach for DaylightHoursSkill on its own — naming it explicitly also works, and is the way to force the call.

Connecting

One server URL covers every skill in the catalog, including this one. Authorization is OAuth: the client opens a browser once, and there is no key to paste into a config file.

{
  "mcpServers": {
    "vervekit": {
      "url": "https://api.vervekit.com/v1/mcp"
    }
  }
}

Per-client setup — Claude, Cursor, VS Code, ChatGPT — is on the MCP setup page.

Arguments

These are the properties on the tool's inputSchema, so a well-behaved client validates them before the call is made. Premium arguments are accepted on every plan but only take effect on plans that include them.

Argument	Type	Description
`latitude`Required	number	Latitude of the location range -90–90
`longitude`Required	number	Longitude of the location range -180–180
`date`OptionalPremium	string	Date in YYYY-MM-DD format (defaults to today) date

What the model gets back

The result carries a structuredContent object matching the tool's declared outputSchema, so a client reads fields without parsing prose. status is "ok" and error is null on success; a null field means the value was not available for that input, not that the call failed.

Result

{
  "status": "ok",
  "error": null,
  "data": {
    "date": "2024-06-21",
    "location": {
      "latitude": 40.7128,
      "longitude": -74.006
    },
    "condition": "Normal",
    "description": "Standard sunrise and sunset",
    "sunrise": "09:25:09",
    "sunset": "24:30:44",
    "daylight_duration": {
      "total_minutes": 905.58,
      "hours": 15,
      "minutes": 5,
      "formatted": "15:05:00"
    },
    "day_of_year": 173,
    "is_valid": true
  }
}

Response fields

Paths are relative to data. Premium fields are absent rather than zeroed on plans that do not include them, so check for presence instead of comparing to 0.

Field	Type	Example	Description
`date`	string	`2024-06-21`	The requested date for daylight calculation
`location`	object	`{…}`
`location.latitude`	number	`40.7128`	Location latitude coordinate used for calculation
`location.longitude`	number	`-74.006`	Location longitude coordinate used for calculation
`condition`Premium	string	`Normal`	Special solar condition at location, e.g., polar day
`description`	string	`Standard sunrise and sunset`	Human-readable description of solar conditions
`sunrise`	string	`09:25:09`	Sunrise time in HH:MM:SS format
`sunset`	string	`24:30:44`	Sunset time in HH:MM:SS format
`daylight_duration`	object	`{…}`
`daylight_duration.total_minutes`Premium	number	`905.58`	Total daylight duration in minutes with decimal precision
`daylight_duration.hours`	number	`15`	Daylight hours component as integer
`daylight_duration.minutes`	number	`5`	Remaining daylight minutes component after hours
`daylight_duration.formatted`	string	`15:05:00`	Formatted daylight duration as HH:MM:SS string
`day_of_year`	number	`173`	Julian day number of the year, one to 366
`is_valid`	boolean	`true`	Indicates whether calculation is valid for location

Failure modes

Errors come back as tool errors carrying a sentence the model can act on, not a bare status code. Error handling covers the full list.

Status	What it means
`400` / `422`	The arguments did not validate. The message names the offending one.
`401`	The OAuth session is invalid or expired — reconnect the server.
`403`	Blocked by a key restriction or an IP allow-list. Never a bad identity.
`404`	This skill is not part of VerveKit. Check the catalog.
`429`	Out of credits, or a brief rate limit. The message tells them apart.

A call costs 2 credits each time the tool actually runs; a model that reasons about the tool without calling it costs nothing.

Use cases

Solar Optimization: Calculate daylight hours for solar panel optimization and energy production forecasting based on geographic location
Activity Planning: Plan outdoor activities and events based on accurate sunset and sunrise times for any location and date
Weather Apps: Build weather and astronomy applications with precise daylight duration calculations and solar position data
Photography Scheduling: Schedule photography sessions based on golden hour timing, blue hour, and optimal natural lighting conditions

Other ways to use Daylight Hours Skill

Set up Daylight Hours Skill on VerveKit, or reach the same source a different way. Your VerveKit account and credits work on all of them — one key, one balance.

Call it as a REST APIOne HTTPS endpoint and an x-api-key header, with SDKs for Node, Python and .NET.APIVerve →Reference →

Google Sheets or ExcelA =VERVE() formula fills a column — no script, no export, recalculates in place.VerveSheets →Reference →

Ground an agent on itA cited, machine-checkable fact your model can't produce on its own.VerveContext →Reference →