IPMA MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_weather_forecastC | Obter previsão meteorológica para uma cidade específica em Portugal |
| get_weather_warningsB | Obter avisos meteorológicos ativos em Portugal |
| get_seismic_dataC | Obter dados sísmicos recentes |
| get_locationsB | Listar todas as cidades/locais disponíveis para previsão |
| get_weather_stationsC | Obter dados de observação das estações meteorológicas |
| get_uv_forecastC | Obter previsão do índice UV |
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 6 tools
Each tool has a clearly distinct purpose: get_locations lists available cities, get_seismic_data provides seismic data, get_uv_forecast gives UV forecasts, get_weather_forecast offers weather forecasts, get_weather_stations shows station observations, and get_weather_warnings lists active warnings. There is no overlap or ambiguity in their functions.
All tools follow a consistent verb_noun pattern with 'get_' as the prefix, followed by a descriptive noun (e.g., get_locations, get_seismic_data). This uniformity makes the tool set predictable and easy to understand.
With 6 tools, the server is well-scoped for weather and seismic forecasting in Portugal. Each tool serves a specific, necessary function without redundancy, making the count appropriate for the domain.
The tool set covers key aspects like forecasts, warnings, seismic data, and station observations, but lacks update or delete operations, which are not essential for this read-only data domain. Minor gaps, such as historical data queries, exist but do not hinder core functionality.