weather-israel-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| ANTHROPIC_API_KEY | Yes | API key for Anthropic (required for the MCP server to function) |
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 |
|---|---|
| get_israel_weatherA | מביא תחזית מזג אויר לעיר בישראל Args: city: שם העיר בעברית (לדוגמא: תל אביב, ירושלים, חיפה) |
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 1 tool
With only one tool, there is no ambiguity. The tool's purpose is clear and distinct.
Single tool follows a clear verb_noun pattern (get_israel_weather). Consistency is inherent.
One tool is minimal but acceptable for a focused weather server. However, it feels borderline thin for a comprehensive weather service.
Only a single forecast tool is provided; missing current conditions, alerts, or other common weather operations. Significant gaps exist for the domain.