HeatShield
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
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 |
|---|---|
| geocode_locationA | Get the latitude and longitude for a city, address, or location. Always use this tool first if you only have a city name and need coordinates for the other tools. Args: query: The name of the city or location (e.g., "Karlsruhe, Germany") |
| get_weather_and_heat_riskB | Fetch live weather data (temperature, humidity, UV index) and a calculated WHO/CDC heat risk level. Requires latitude and longitude. |
| get_air_qualityA | Fetch live air quality data (PM2.5, PM10, AQI) to assess respiratory safety during heat waves. Requires latitude and longitude. |
| find_cooling_spotsA | Use spatial analytics to find nearby cooling shelters (parks, pools, libraries, fountains). Requires latitude, longitude, and an optional radius in meters. |
| get_heat_safety_adviceA | Get WHO/CDC safety recommendations based on the current heat risk level and the user's activity. Args: heat_risk_level: Must be LOW, MODERATE, HIGH, or EXTREME (obtained from get_weather_and_heat_risk) activity_type: e.g., "jogging", "construction work", "elderly care", "general" |
| get_heatwave_forecastB | Fetches a 7-day weather forecast and calculates a Climate Aggravation Risk by correlating high temperatures with drought/soil moisture conditions. Use this to predict upcoming heatwaves and warn the user. |
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 targets a distinct function: geocoding, current heat risk, air quality, cooling spots, safety advice, and heatwave forecast. There is no overlap that would confuse an agent's selection.
All tools follow a clear verb_noun pattern (geocode_location, get_weather_and_heat_risk, get_air_quality, find_cooling_spots, get_heat_safety_advice, get_heatwave_forecast). The verbs (geocode, get, find) are appropriate and consistently placed.
With 6 tools, the server is well-scoped for a heat health domain. Each tool provides essential functionality without redundancy or bloat, making the set easy to navigate.
The tool set covers the full user workflow: location to coordinates, current heat risk, air quality, cooling shelter discovery, safety advice, and upcoming heatwave prediction. No obvious gaps exist for typical heat safety use cases.