Skip to main content
Glama
israel-weather-mcp

israel-weather-mcp

by YL4279

open_weather_forecast_israel

Opens the Israeli weather forecast website so you can access real-time city forecasts and current conditions.

Instructions

פותח את אתר התחזית.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "open_weather_forecast_israel"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.7/5.0
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are provided, so the description carries the full disclosure burden, and 'opens the site' reveals almost nothing: whether this is a UI navigation, a data fetch, or a state-changing action, and whether it has side effects, is left unstated. With zero parameters there is no risk of contradiction, but the behavioral profile is essentially undocumented.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single short sentence with no padding, so it is certainly concise and front-loaded. However, the brevity reflects under-specification rather than efficiency — the one sentence could have been spent resolving the ambiguity about what 'open' actually does.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists, so return values need not be explained, and with no parameters the call mechanics are trivial. Still, for a tool embedded in a four-tool weather family, the description leaves the agent unable to tell what this call accomplishes relative to its siblings or what 'opening' entails.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool takes zero parameters, so there are no parameter semantics for the description to explain; the baseline for a no-parameter tool applies. Nothing in the description misrepresents the (empty) input surface.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The Hebrew description 'פותח את אתר התחזית' ('opens the forecast site') names an action and a resource, so the general purpose is inferable. But 'open' is ambiguous (navigate to a page? launch a browser? fetch data?) and nothing distinguishes it from the sibling get_weather_forecast_israel, which sounds like it retrieves the same forecast.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No statement of when to use this instead of get_weather_forecast_israel, enter_weather_forecast_city_israel or select_weather_forecast_city_israel, and no prerequisites or sequencing hints. The agent must guess the ordering of these four tools from their names alone.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.