Skip to main content
Glama

select_weather_forecast_city_israel

Select the first city from the Israeli weather forecast list and navigate to its detailed forecast page for current conditions.

Instructions

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

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • The tool 'select_weather_forecast_city_israel' is registered via @mcp.tool() decorator and implemented as an async function. It uses Playwright to click the first autocomplete suggestion on the weather forecast website, navigates to the detailed forecast page, and returns a success/error message.
    @mcp.tool()
    async def select_weather_forecast_city_israel() -> str:
        """
        שלב 3: בוחר את העיר הראשונה מהרשימה ועובר לדף התחזית המפורט.
        """
        page = await browser_mgr.ensure_page()
        # סלקטור גמיש לרשימת ההשלמה
        item_selector = ".autocomplete-items div, .autocomplete-suggestion"
        
        try:
            await page.wait_for_selector(item_selector, timeout=7000)
            
            # לחיצה והמתנה לטעינת הדף החדש (networkidle מבטיח שהמידע נטען)
            async with page.expect_navigation(wait_until="networkidle", timeout=15000):
                await page.click(item_selector)
                
            return "SUCCESS: העיר נבחרה ודף התחזית נטען בהצלחה."
        except Exception:
            # גיבוי: לחיצה על Enter אם הרשימה לא נלחצה
            await page.keyboard.press("Enter")
            await asyncio.sleep(4)
            return "SUCCESS: בוצעה בחירה באמצעות Enter. בדוק אם הדף נטען."
  • The tool is registered using the @mcp.tool() decorator on line 93, which binds it to the FastMCP server instance named 'mcp' created on line 6.
    @mcp.tool()
Behavior2/5

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

With no annotations provided, the description carries full burden but only states the action (select and navigate). It does not disclose behavioral traits such as side effects, state changes, or whether it requires prior steps. The description is minimal and lacks depth for an unannotated tool.

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 short sentence that directly states the tool's action. No redundant words, efficiently communicates purpose. It is appropriately sized for the simple no-parameter tool.

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?

Given the tool has no parameters and an output schema exists (which covers return values), the description captures the essential action. However, it could benefit from noting that this is part of a multi-step workflow (as implied by 'Step 3') and what the detailed forecast page contains.

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, and schema description coverage is 100% trivially. The description adds no parameter information, but per rules, 0 parameters baseline is 4. No additional meaning needed.

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 that the tool selects the first city from a list and navigates to the detailed forecast page, aligning with the tool name. It differentiates from siblings like 'enter_weather_forecast_city_israel' which implies manual entry, but lacks context on what list is being used.

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 only says 'Step 3', implying a sequence but no explicit guidance on when to use this tool versus alternatives like 'enter_weather_forecast_city_israel' or 'get_weather_page_content'. No when-not or prerequisite information is provided.

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