Overview
Weather works by querying a large database of weather data to retrieve the current weather for a location. It returns the weather data in a structured format.
The tool
Once your client is connected to the VerveKit server, this appears in its tool list as WeatherSkill. 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.
{
"name": "WeatherSkill",
"arguments": {
"city": "San Francisco"
}
}You do not name the tool yourself; the model picks it. Asking about San Francisco in the terms this skill covers is enough for it to reach for WeatherSkill 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"
}
}
}https://api.vervekit.com/v1/mcpPer-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 |
|---|---|---|
cityRequired | string | The city for which you want to get the current weather (e.g., San Francisco) |
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.
{
"status": "ok",
"error": null,
"data": {
"tempC": 13.3,
"tempF": 55.9,
"windMph": 4.7,
"windKph": 7.6,
"windDegree": 273,
"windDir": "W",
"pressureMb": 1022,
"pressureIn": 30.17,
"precipMm": 0,
"precipIn": 0,
"feelslikeC": 13,
"feelslikeF": 55.3,
"visKm": 16,
"visMiles": 9,
"gustMph": 7.2,
"gustKph": 11.6
}
}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 |
|---|---|---|---|
tempC | number | 13.3 | Current temperature in degrees Celsius |
tempF | number | 55.9 | Current temperature in degrees Fahrenheit |
windMph | number | 4.7 | Wind speed in miles per hour |
windKph | number | 7.6 | Wind speed in kilometers per hour |
windDegree | number | 273 | Wind direction in degrees (0-360) |
windDir | string | W | Wind direction as compass point (N, S, E, W, etc.) |
pressureMbPremium | number | 1022 | Atmospheric pressure in millibars |
pressureInPremium | number | 30.17 | Atmospheric pressure in inches of mercury |
precipMmPremium | number | 0 | Precipitation amount in millimeters |
precipInPremium | number | 0 | Precipitation amount in inches |
feelslikeCPremium | number | 13 | Apparent temperature in degrees Celsius |
feelslikeFPremium | number | 55.3 | Apparent temperature in degrees Fahrenheit |
visKmPremium | number | 16 | Visibility distance in kilometers |
visMilesPremium | number | 9 | Visibility distance in miles |
gustMphPremium | number | 7.2 | Wind gust speed in miles per hour |
gustKphPremium | number | 11.6 | Wind gust speed in kilometers per hour |
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 10 credits each time the tool actually runs; a model that reasons about the tool without calling it costs nothing.
Use cases
- Weather App
- Use the Weather API to get current weather for a weather app. Use the data to display weather information, provide forecasts, and offer alerts
- Travel App
- Get current weather by using the Weather API for a travel app. Use the data to plan trips, check conditions, and prepare for travel
- Outdoor Activities
- Plan outdoor activities by using the Weather API to get current weather. Use the data to schedule events, organize trips, and optimize experiences
Other ways to use Weather Skill
Set up Weather 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.
Related
Pages that use this skill:
- GraphQLPlatform
More in Weather: