windy-webcams-mcp-server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| WINDY_API_KEY | Yes | Windy API key for accessing the Webcam API |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_webcamsC | Search for webcams with various filters (location, category, etc.) |
| get_webcamA | Get detailed information about a specific webcam by ID |
| get_webcams_by_locationA | Get webcams from a specific location (country, region, continent, or city) |
| get_webcams_by_categoryB | Get webcams from specific categories |
| get_nearby_webcamsB | Find webcams near specific coordinates |
| get_map_clustersA | Get webcam clusters optimized for map display |
| get_categoriesA | Get available webcam categories for filtering |
| get_countriesB | Get available countries with webcams |
| get_regionsA | Get available regions with webcams |
| get_continentsB | Get available continents with webcams |
| export_all_webcamsA | Get basic information about all available webcams |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 11 tools
Most tools target distinct query types (by ID, by location, by category, nearby, map clusters, reference lists), but search_webcams with filters overlaps conceptually with the dedicated by_location/by_category/nearby tools, creating mild ambiguity. The reference-list tools (regions, continents, countries, categories) are clearly distinct.
The dominant pattern is get_webcams_by_* and get_<reference-entity>, which is consistent and predictable. Two exceptions, search_webcams and export_all_webcams, break the pattern but are still clear and understandable.
With 11 tools, the server is well-scoped for a read-only webcam data API. Each tool serves a clear purpose, and the count is within the ideal 3-15 range without feeling bloated.
The surface covers the full range of likely queries: reference data, search, detail lookup, filtered listing by location/category, proximity search, map-friendly clusters, and bulk export. For a read-only public webcam API, there are no obvious dead ends or missing operations.