agentweb-mcp

weather_forecast

Retrieve current weather conditions and up to 14-day forecast for any city worldwide, including temperature, humidity, wind, precipitation, UV index, and packing advisories.

Instructions

Get weather forecast for any city worldwide. Returns current conditions (temperature, humidity, wind, precipitation) plus daily forecast up to 14 days with high/low temps, rain chance, UV index, sunrise/sunset, and packing advisories. Results in ~1 second.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "city": "<city>"
    },
    "name": "weather_forecast"
  }
}

Input Schema

Name	Required	Description	Default
`city`	Yes	City name (e.g. 'Rome', 'Tokyo', 'New York')
`days`	No	Number of forecast days (1-14, default: 3)
`units`	No	Temperature unit (default: celsius)	celsius

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.17.0Jun 21, 2026

TDQS

A4.2/5.0

Behavior4/5

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

No annotations, but description adds behavioral details: 'Results in ~1 second' and lists returned data fields (current conditions, daily forecast, packing advisories). Provides good insight into tool behavior.

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?

Two front-loaded sentences, no fluff. Every part adds value: purpose, return data, performance note.

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?

No output schema, but description explains return content thoroughly (current conditions, daily details, packing advisories). Missing error handling or rate limits, but adequate for typical use.

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?

Schema coverage is 100%, baseline 3. Description adds context: 'daily forecast up to 14 days' clarifies days param, and mentions 'packing advisories' not in schema. Enhances parameter understanding.

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?

Clearly states 'Get weather forecast for any city worldwide' with specific verb and resource. Distinguishes from sibling tools like search_flights and search_hotels by being a unique weather tool.

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?

No explicit when-to-use or alternatives, but the description implies use for any city. Lacks exclusions or guidance on 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.