weather-Israel
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| GEMINI_API_KEY | Yes | Your Google Gemini API key (free key: https://aistudio.google.com/apikey) | |
| WEATHER_HEADLESS | No | Optional – set to '1' to run the browser without a visible window | 0 |
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 |
|---|---|
| open_weather_forecast_israelB | Open Chrome and navigate to the Israel weather forecast page. |
| enter_weather_forecast_city_israelA | Types the specific city name into the search bar. Requires 'city' argument. Must be called right after opening the browser. |
| select_weather_forecast_city_israelA | Clicks the first suggestion in the search dropdown menu. Call this ONLY after enter_weather_forecast_city_israel has finished executing. Takes no arguments. |
| get_weather_page_content_israelA | Extracts and returns the visible text content of the currently open weather page. Call this after navigating to a city forecast to give the LLM the actual weather data. |
| get_israel_forecastA | One call that does the whole flow: open the forecast site, search for 'city', pick the first match, and return the cleaned forecast text. Use this for a normal weather question - it keeps the conversation short. The separate open/enter/select tools are for stepping through the browser manually. |
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 5 tools
The high-level get_israel_forecast tool is clearly distinct from the manual browser steps, and its description explicitly directs agents to use it for normal queries. The four step-by-step tools are sequential and have clear dependencies, so an agent can distinguish them. However, both paths ultimately return weather data, creating slight overlap in purpose.
All tools end with '_israel' and use clear verbs (get, open, enter, select, get). The pattern is mostly verb + object + israel, though get_israel_forecast breaks the order (get + israel + forecast) and some names are verbose. Overall, the naming is readable and predictable, with only minor deviations.
With 5 tools, the server is well-scoped. The high-level tool provides a quick path, while the four low-level tools enable manual browser control. This is a reasonable size that avoids redundancy and keeps the surface manageable.
The tool set covers the full weather retrieval workflow: the high-level tool handles everything in one call, and the manual tools cover open, search, select, and read steps. There are no missing operations for the stated purpose of fetching Israel weather forecasts, and the domain is read-only, so no CRUD gaps exist.