Daylight Hours Skill
The tool
The API handles special conditions like polar days and polar nights, providing accurate solar calculations based on latitude, longitude, and date.
Once your client is connected to the VerveKit MCP server, this appears in its tool list as DaylightHoursSkill. It is read-only and open-world: it fetches, it never mutates anything on your side, so most clients will call it without asking you to confirm.
{
"name": "DaylightHoursSkill",
"arguments": {
"latitude": "40.7128",
"longitude": "-74.006"
}
}What that looks like in a conversation
You don't name the tool — the model picks it. Asking about 40.7128 in the terms this source covers is enough for it to reach for DaylightHoursSkill on its own.
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"
}
}
}https://api.vervekit.com/v1/mcpPer-client setup — Claude Desktop, 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.
| Argument | Type | Example | Description |
|---|---|---|---|
latitudeRequired | number | 40.7128 | Latitude of the location |
longitudeRequired | number | -74.006 | Longitude of the location |
datePremium | string | 2024-06-21 | Date in YYYY-MM-DD format (defaults to today) |
What the model gets back
The result carries a structuredContent object matching the tool's declared outputSchema, so a client can read fields without parsing prose. status is "ok" on success and error is null; a null field means the value wasn't available for that input, not that the call failed.
{
"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
}
}Fields
| 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 |
conditionPremium | 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_minutesPremium | 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 with a sentence the model can act on, not a bare status code.
| Status | What it means |
|---|---|
400 / 422 | The arguments didn't validate. The message names the offending one. |
401 | The OAuth session is invalid or expired — reconnect the server. |
403 | Out of credits. Not a bad key — the month's allowance is spent. |
404 | This skill isn't part of VerveKit. Check the catalog. |
429 | Brief rate limit. Retrying after a moment succeeds. |
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.
Frequently asked questions
Do I have to tell the agent to use DaylightHoursSkill?
No. The tool's name and description are in the model's context once the server is connected, so it selects the tool when the question calls for it. Naming it explicitly works too and is useful when you want to force the call.
Does connecting the server expose every tool at once?
Yes — one connection lists the whole VerveKit catalog. Clients with a tool budget can usually filter the list; the credit cost is per call, so an unused tool costs nothing.
What does a call cost?
1 credit each time the tool actually runs. A model that reasons about the tool without calling it costs nothing.
Is there a REST version of this?
Yes — the same source is available as a plain HTTPS endpoint on APIVerve, linked above. Same data, same credits, same account.