Israel Weather MCP
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 |
|---|---|
| open_weather_forecast_israelA | Open the Israeli weather forecast site in a browser (weather2day.co.il/forecast). Call this first before typing a city name. |
| enter_weather_forecast_city_israelA | Type an Israeli city name into the weather2day forecast search box. Args: city_name: City name in Hebrew or English (e.g. 'ירושלים', 'חיפה', 'Tel Aviv'). |
| select_weather_forecast_city_israelA | Select the first city suggestion from the autocomplete list and open its forecast page. |
| get_weather_page_contentA | Extract and clean the current forecast page text so the LLM can answer the user (RAG step). Call this after the city forecast page is open. |
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 4 tools
Each tool represents a distinct step in a clear sequential workflow: open site, enter city, select suggestion, extract content. There is no overlap in functionality, and the dependencies are explicitly described in the tool descriptions.
All names use snake_case, but the pattern is mixed: the first three follow 'verb_weather_forecast_[city_]israel', while the fourth breaks the pattern with 'get_weather_page_content'. The verbs are consistent with their actions, but the structural inconsistency is notable.
Four tools is perfectly scoped for the domain. Each tool covers a necessary step in retrieving weather forecast data from the site, with no extraneous or redundant tools.
The tool set fully covers the intended workflow: open site → enter city → select suggestion → extract content. It allows for multiple city queries by repeating the enter/select steps, and there are no obvious dead ends or missing operations within the stated purpose.