Skip to main content
Glama
wttr.in Weather MCP

wttr.in Weather MCP

by zhbjerry

wttr_request

Retrieve weather forecasts and moon-phase data from wttr.in in JSON, text, HTML, Prometheus, PNG, or custom formats, with query options for locations and display settings.

Instructions

Access documented wttr.in output formats and query options, including JSON, text, HTML, Prometheus, PNG, custom formats, and moon phase emoji.

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

Input Schema

NameRequiredDescriptionDefault
formatNoOutput format. Use moon for JSON moon phase data, or use formatCode %m for the moon emoji.json
paramsNoAdditional wttr.in query parameters, such as lang=zh, m, u, M, or transparency=150.
locationNoCity, airport code, coordinates, IP, domain, Moon, or multiple locations separated by :. Omit for server IP location.
formatCodeNowttr.in format code, such as j1, j2, p1, 3, or %m.
shortOptionsNoShort wttr.in options, or PNG options such as 0tqp.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.1

TDQS

C2.7/5.0
Behavior2/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 implies a proxied HTTP request to a third-party service (wttr.in) but says nothing about read-only nature, rate limits, timeouts, error behavior, or that some formats (PNG) return binary rather than text - all material 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.

Conciseness4/5

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

A single tight sentence with the resource front-loaded. The trailing enumeration of formats partly duplicates the schema enum and could be trimmed, but the description is not padded.

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 five parameters, one of them a free-form nested object keyed by arbitrary names, and no output schema, the agent gets no picture of what actually comes back per format or how 'params' keys are interpreted. The rich schema compensates for most parameter gaps, but the absence of any return-shape hint leaves a real hole.

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%, with each of the five parameters documented in-schema including the format enum and passthrough params. The description only repeats the format list already in the enum and adds no new meaning about location syntax, formatCode, or shortOptions, so the baseline of 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The resource is specific (wttr.in output formats and query options) and the enumerated formats give a concrete sense of what can be requested. However, the verb 'Access' is vague - it never states plainly that this retrieves weather data - and nothing distinguishes it from the sibling get_weather, so the agent must infer the boundary itself.

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?

There is no when-to-use guidance at all: no mention of when to pick this over get_weather, no prerequisites, no note about which formats suit which purpose. The format enum in the schema implies choice, but the description offers no selection logic.

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