Skip to main content
Glama
Sign In
Weather-MCP

Weather-MCP

by Efrat-Fr
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

open_weather_forecast_israel

Retrieve Israel's weather forecast by opening the official forecast website in a browser. Enables agents to answer weather queries for Israeli locations.

Instructions

Open a browser and navigate to the Israeli weather forecast website.

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

A3.5/5.0
Behavior3/5

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

With no annotations, the description must carry the behavioral burden. It does disclose that the tool launches a browser and navigates to a website, which is the core behavior. However, it does not mention side effects like whether an existing browser session is reused, whether the page loads before returning, or what happens on navigation failure.

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

Conciseness5/5

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

The description is a single, clear sentence with no redundant words. The action and target are front-loaded and immediately understandable.

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

Completeness4/5

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

For a zero-argument browser-navigation tool, the description is largely complete: it identifies the action and target. The exact URL is not specified, but the 'Israeli weather forecast website' is enough of a target, and an output schema is present so return-value details are not required. Minor lack of contextual guidance about when to call it is already captured in usage_guidelines.

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 input schema has zero parameters, so there is no parameter semantics burden on the description. The baseline of 4 applies because there is nothing for the description to clarify about arguments.

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

Purpose4/5

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

The description clearly states the action ('Open a browser and navigate') and the resource ('Israeli weather forecast website'), making the tool's purpose obvious. It does not explicitly distinguish itself from sibling tools, but the naming and 'open browser' action imply a distinct initial navigation step.

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?

The description gives no guidance on when to use this tool versus the siblings like enter_weather_forecast_city_israel or get_weather_forecast_content_israel. There is no mention of prerequisites, ordering, or contexts where this tool is the appropriate choice.

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

Deploy Server

Other Tools