Skip to main content
Glama
Sign In
Weather Israel MCP Server

Weather Israel MCP Server

by yael3222664-alt
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

select_weather_forecast_city_israel

Selects the first city in the dropdown list to initiate a weather forecast query for Israel.

Instructions

Clicks/selects the first item in the dropdown list of cities.

Returns: A message indicating success or failure

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": "select_weather_forecast_city_israel"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior2/5

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

No annotations provided, so description must disclose all behavioral traits. It simply states 'clicks/selects' and returns success/failure, but lacks details on side effects (e.g., page changes, error states if dropdown empty). Minimal transparency for a UI interaction.

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?

Description is concise with two sentences covering action and return. No unnecessary words. Could benefit from a more structured format, but efficiency is good.

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?

With an output schema existing, the description need not explain return values. However, it omits error conditions, prerequisites (e.g., dropdown must be visible), and how it interacts with sibling tools. Adequate but not comprehensive for a UI automation tool.

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

Parameters3/5

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

Input schema has no properties, so schema coverage is 100%. Baseline 3 applies. The description adds no parameter info because none exist; it correctly describes the tool's action without needing param details.

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 identifies the action (clicks/selects) and the target (first item in dropdown list of cities). It distinguishes from siblings like 'enter_weather_forecast_city_israel' which likely types input. However, it could be more explicit about the tool's role in the workflow.

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 on when to use this tool versus alternatives. It does not mention prerequisites or when selection is appropriate, leaving the agent to infer usage context.

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