Weather Israel 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
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 | Step 1: Opens the browser and navigates to the Israel weather forecast homepage. Call this first before searching for a city. |
| enter_weather_forecast_city_israelA | Step 2: Enters the requested city name into the search field on the weather site. Args: city_name: The name of the city in Hebrew (e.g. 'ירושלים', 'תל אביב', 'חיפה'). |
| select_weather_forecast_city_israelA | Step 3: Selects the first city result from the autocomplete dropdown list. Call this right after enter_weather_forecast_city_israel. |
| get_weather_forecast_content_israelA | Step 4: Extracts text content from the loaded city weather page. Call this after select_weather_forecast_city_israel. |
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 is a distinct step in a sequential flow—open, enter, select, get—and the step numbers in descriptions make boundaries clear. The two city-related tools (enter and select) are slightly similar in name but their action verbs and descriptions differentiate them well.
All tools follow a snake_case verb-first pattern and share a weather_forecast_israel domain prefix. Minor inconsistencies exist: open_weather_forecast_israel omits 'city,' and get_weather_forecast_content_israel uses 'content' instead of 'city,' but the pattern remains predictable.
Four tools map directly to the four required browser-automation steps, and none feel redundant. This is a well-scoped size for a simple weather lookup workflow.
The tool set covers the full flow from opening the weather site to extracting the city forecast text, so agents can complete a basic lookup. It lacks structured forecast data or alternate input formats, but these are not core to the described workflow.