Skip to main content
Glama

open_weather_forecast_israel

Opens the Israeli weather website and manages initial messages for real-time weather data retrieval.

Instructions

שלב 1: פותח את אתר מזג האוויר בישראל ומטפל בהודעות ראשוניות.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • The handler function for the 'open_weather_forecast_israel' tool. Uses Playwright to navigate to a weather forecast website, accepts cookies if prompted, and returns a success message.
    @mcp.tool()
    async def open_weather_forecast_israel() -> str:
        """
        שלב 1: פותח את אתר מזג האוויר בישראל ומטפל בהודעות ראשוניות.
        """
        page = await browser_mgr.ensure_page()
        await page.goto(FORECAST_URL, wait_until="domcontentloaded")
        
        # ניסיון לסגור הודעת קוקיז אם קיימת
        try:
            cookie_btn = page.locator("#cookie-accept")
            if await cookie_btn.is_visible():
                await cookie_btn.click(timeout=2000)
        except:
            pass
            
        return "SUCCESS: האתר פתוח. כעת ניתן להזין שם עיר."
  • The tool is registered via the @mcp.tool() decorator on the async function open_weather_forecast_israel.
    @mcp.tool()
Behavior2/5

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

No annotations are provided, and the description does not disclose behavioral traits such as whether the tool is destructive, requires authentication, or its side effects. It simply states it opens a site and handles messages.

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?

The description is very concise (one line), but it lacks structure and could be more informative without adding length. It is not overly verbose but could benefit from clarity.

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?

Given no parameters and an output schema (not detailed), the description might be sufficient for a simple open action. However, it does not explain what 'handles initial messages' means or provide context for the workflow, leaving it incomplete.

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 has no parameters, so the description does not need to add parameter information. According to guidelines, 0 parameters yields a baseline of 4.

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 description states it opens a weather website in Israel and handles initial messages, but 'handles initial messages' is vague. Given sibling tools, it is likely the first step in a workflow, but the purpose is not fully clear.

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 usage guidelines provided. The description only says 'Step 1', implying it's the first step, but there is no explicit guidance on when to use this tool versus siblings or when not to use it.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/lea-blum/MCP'

If you have feedback or need assistance with the MCP directory API, please join our Discord server