Skip to main content
Glama
Sign In
MCP Weather Assistant

MCP Weather Assistant

by yehudit-alfa
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

open_weather_forecast_israel

Opens the browser to display the main weather forecast page for Israel, showing 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

A3.5/5.0
Behavior2/5

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

No annotations are provided. The description only says 'opens browser and navigates', which implies a read-like navigation but does not disclose any behavioral traits such as whether it returns data or requires authentication.

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 Hebrew sentence with no wasted words. It is front-loaded with the action.

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

Completeness3/5

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

The description lacks detail about the output schema, which exists. It does not explain what the tool returns (e.g., a page object or the weather data). This is a gap given that sibling tools provide more specific actions.

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?

There are no parameters, so the schema coverage is 100%. With 0 parameters, baseline is 4, and the description adds no parameter info which is fine.

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

Purpose5/5

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

The description clearly states the tool opens the browser and navigates to the main weather page in Israel, which is a specific verb+resource. It distinguishes from siblings like 'enter_weather_forecast_city_israel' which are more specific.

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 guidance is provided on when to use this tool versus alternatives (e.g., enter_weather_forecast_city_israel or extract_weather_data_israel). The agent must infer from the name.

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