AEMET-MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| AEMET_API_KEY | Yes | Your AEMET API key for accessing weather data |
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 | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_municipality_codeA | Search Spanish municipalities by name or province (accent-insensitive, typo-tolerant). Args: nombre: Partial or approximate name of a municipality or province. Returns: A list of matching municipalities with their codes and provinces. |
| get_daily_forecastB | Get the daily weather forecast for a Spanish municipality. Args: municipality_code: AEMET municipality code (e.g., "28079" for Madrid) |
| get_station_dataB | Obtain specific weather data for a weather station. Args: station_id: Station identifier (e.g., "8416Y" for Valencia)) |
| get_station_listA | Get a list of all available weather stations or filter by one or more search terms, including approximate matches. Args: search_terms: Optional terms (space or comma separated) to filter stations by name or province. |
| find_nearby_stationsB | Find weather stations within a given radius (in km) from a given geographic coordinate. Args: lat: Latitude in decimal degrees (e.g., 43.36) lon: Longitude in decimal degrees (e.g., -8.41) radio_km: Search radius in kilometers |
| get_historical_dataA | Obtain historical meteorological data for a specific station. Args: station_id: Identifier of the station (e.g. "3195" for Madrid Retiro) start_date: Start date in format YYYYY-MM-DD end_date: End date in format YYYYY-MM-DD |
| monthly_climate_dataC | Retrieve monthly climatological data for a specific weather station. Args: station_id: Weather station identifier (e.g., "3195" for Madrid Retiro). year: Year (YYYY). month: Month (1-12). Returns: A JSON with the monthly climate summary. |
| solve_beach_codeC | Search beaches by name, province, or municipality. Args: nombre: Search string (accent-insensitive) tipo: One of 'playa', 'provincia', or 'municipio' |
| get_beach_data_uvA | Query information on beaches or UV index from AEMET. Args: name_or_code: Partial or full name of the beach, or its BEACH_ID. Also accepts 'list' or 'list:'. dias_frc: Number of forecast days, starting form 0, which means 0 days from today, to 4, which means 4 days from today. query_type: 'beach' for forecast, 'UV_index' for UV index, must be in english. Returns: Requested information or list of matches. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| obtener_datos_lluvia_municipio | Obtiene los datos históricos de precipitación para un municipio español específico utilizando la estación meteorológica más cercana de AEMET. Args: municipio: Nombre del municipio español (ej: "Madrid", "Sevilla") fecha_inicio: Fecha de inicio en formato YYYY-MM-DD (ej: "2023-01-01") fecha_fin: Fecha de fin en formato YYYY-MM-DD (ej: "2023-12-31") Returns: Prompt estructurado para obtener y analizar los datos de precipitación |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 9 tools
Every tool targets a distinct resource or operation: stations (find, list, get data, historical, monthly), beaches (search, get data), daily forecast, and municipality search. No overlapping purposes.
Naming conventions are mixed: some use 'get_', others 'find_', 'search_', 'solve_', and one is adjective_noun ('monthly_climate_data'). While all are descriptive, the pattern is inconsistent.
Nine tools is well-scoped for a weather data API covering stations, beaches, forecasts, historical data, and municipality lookup. Each tool serves a clear purpose without unnecessary duplication.
The tool set covers core weather queries: station listings, current data, daily forecasts, historical and monthly climate, beach info, and UV index. Missing are alerts or radar, but the surface is largely complete for common use cases.