Skip to main content
Glama
wttr.in Weather MCP

wttr.in Weather MCP

by zhbjerry

get_weather

Retrieve current weather and a 1-3 day forecast from wttr.in for a specified city, airport code, or coordinates, or omit location to use the server's IP-based location.

Instructions

Get current weather and a forecast of up to three days from wttr.in. Omit location to use the server IP location.

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

Input Schema

NameRequiredDescriptionDefault
daysNoNumber of forecast days to return, from 1 to 3.
languageNoOptional wttr.in language code, for example zh or en.
locationNoCity, airport code, or latitude,longitude. Omit for server IP location.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.1

TDQS

A3.5/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full burden. It does disclose the data source (wttr.in) and the hard three-day forecast cap, which are useful behavioral facts. It says nothing about rate limits, error behavior, caching, or what the response payload looks like — gaps that matter for a network-backed fetch with no annotation coverage.

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 short sentences with zero filler; the capability statement is front-loaded and the location default follows immediately. Every clause carries information.

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?

For a simple three-parameter lookup with full schema coverage, the description covers invocation adequately. However, with no output schema present, the description never indicates what the returned weather data looks like or how it is structured, and it leaves the relationship to wttr_request unexplained.

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?

Schema description coverage is 100%, so all three parameters are already documented, including the same "omit for server IP location" note the description repeats. The description adds no syntax, format, or default information beyond the schema, so the baseline 3 applies.

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?

"Get current weather and a forecast of up to three days from wttr.in" gives a specific verb (get) and resource (current weather + forecast), plus the upstream data source. It does not distinguish itself from the sibling wttr_request, so an agent cannot tell from the description which of the two to pick.

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 one conditional usage note: "Omit location to use the server IP location." That helps an agent decide how to call it, but there is no when-to-use/when-not guidance and no mention of the wttr_request sibling as an alternative.

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