Skip to main content
Glama

enter_weather_forecast_city_israel

Enter a city name to retrieve the weather forecast for that location in Israel.

Instructions

שלב 2: מזין את שם העיר בשדה החיפוש.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
city_nameYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • The main handler function for the 'enter_weather_forecast_city_israel' tool. It accepts a city_name, navigates to the forecast page if needed, locates the city search input (#city_search_forecast), clears it, types the city name with a delay to trigger autocomplete, and returns a success/error message.
    async def enter_weather_forecast_city_israel(city_name: str) -> str:
        """
        שלב 2: מזין את שם העיר בשדה החיפוש.
        """
        page = await browser_mgr.ensure_page()
        search_selector = "#city_search_forecast"
        
        try:
            # ודוא שאנו בדף הנכון
            if "forecast" not in page.url:
                await page.goto(FORECAST_URL)
    
            await page.wait_for_selector(search_selector, timeout=10000)
            
            # ניקוי יסודי של השדה
            await page.click(search_selector, click_count=3)
            await page.keyboard.press("Control+A")
            await page.keyboard.press("Backspace")
            
            # הקלדה עם השהיה כדי להקפיץ את ה-Autocomplete
            await page.type(search_selector, city_name, delay=150)
            await asyncio.sleep(2) # זמן לרשימה להיפתח
            
            return f"SUCCESS: העיר '{city_name}' הוזנה. כעת בצע בחירה מהרשימה."
        except Exception as e:
            return f"ERROR: הזנת העיר נכשלה: {str(e)}"
  • Registration decorator @mcp.tool() on line 65 registers enter_weather_forecast_city_israel as an MCP tool.
    @mcp.tool()
  • Type signature: city_name is a required str parameter, return type is str.
    async def enter_weather_forecast_city_israel(city_name: str) -> str:
Behavior2/5

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

No annotations exist, and the description only states to enter a city name without disclosing side effects, prerequisites, or error conditions. It fails to describe behavioral traits beyond the basic action.

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

Conciseness4/5

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

The description is a single efficient sentence in Hebrew, front-loading the step number. It is concise but at the cost of informativeness.

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?

Given the presence of sibling tools implying a multi-step workflow, the description lacks context about how this step fits into the larger task. It does not mention the weather forecast domain or the intended outcome.

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

Parameters2/5

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

The input schema has 0% description coverage, and the tool description adds minimal context ('in the search field'). It does not explain format, constraints, or example values, so it barely compensates for the gap.

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 'enter the city name' and references a search field, which matches the tool's name involving weather forecast. However, it does not explicitly connect to the weather context, relying on the name.

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

Usage Guidelines3/5

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

The description includes 'Step 2', implying it follows 'open_weather_forecast_israel' and precedes 'select_weather_forecast_city_israel', providing sequential context but no explicit alternatives or when-not-to-use.

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