Skip to main content
Glama

Weather forecast: current weather and 48-hour hourly forecast for any city or coordinates

weather
Read-only

Current weather by city name, or by latitude and longitude, for any place on Earth: temperature in Celsius, conditions (clear, cloudy, rain, snow), precipitation in mm, wind, humidity, cloud cover and air pressure, plus an hourly forecast for up to 48 hours. Data from the Norwegian Meteorological Institute; city names resolve via Wikidata. Use for travel and event planning, logistics, agriculture and any agent that needs the weather. Example: city=London. Price $0.002/call via x402 USDC or a card key (/credits), first 25 free; failed calls free. Reads or computes only and changes nothing; each call is charged, so repeats are not free.

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

Input Schema

NameRequiredDescriptionDefault
latNoLatitude in decimal degrees, -90 to 90 (with lon, instead of city)
lonNoLongitude in decimal degrees, -180 to 180 (with lat, instead of city)
cityNoCity or place name, e.g. London or Lisbon (used when lat and lon are not given; with no place at all the answer is for London)
hoursNoHours of hourly forecast to return, 1-48 (default 12; 48 covers tomorrow)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / hours / maximum
      Previous value: -9007199254740991New value: +48
    • changedInput schema / properties / hours / minimum
      Previous value: --9007199254740991New value: +1
  2. Changed1 schema field changed
    • changedInput schema / properties / city / description
      Previous value: -"City or place name, e.g. London or Uppsala (used when lat and lon are not given; with no place at all the answer is for London)"New value: +"City or place name, e.g. London or Lisbon (used when lat and lon are not given; with no place at all the answer is for London)"
  3. Changed1 schema field changed
    • changedInput schema / properties / city / description
      Previous value: -"City or place name, e.g. London or Uppsala (used when lat and lon are not given)"New value: +"City or place name, e.g. London or Uppsala (used when lat and lon are not given; with no place at all the answer is for London)"
  4. Changed5 schema fields changed
    • addedInput schema / properties / city
      Added value: +{
      +  "description": "City or place name, e.g. London or Uppsala (used when lat and lon are not given)",
      +  "type": "string"
      +}
    • changedInput schema / properties / hours / description
      Previous value: -"Hours of hourly forecast to return, 1-48 (default 12)"New value: +"Hours of hourly forecast to return, 1-48 (default 12; 48 covers tomorrow)"
    • changedInput schema / properties / lat / description
      Previous value: -"Latitude in decimal degrees, -90 to 90"New value: +"Latitude in decimal degrees, -90 to 90 (with lon, instead of city)"
    • changedInput schema / properties / lon / description
      Previous value: -"Longitude in decimal degrees, -180 to 180"New value: +"Longitude in decimal degrees, -180 to 180 (with lat, instead of city)"
    • removedInput schema / required
      Removed value: -[
      -  "lat",
      -  "lon"
      -]
  5. Added

TDQS

A4.3/5.0
Behavior5/5

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

Beyond the annotations (readOnly, openWorld, non-destructive), the description discloses the data provider (Norwegian Meteorological Institute), city-name resolution via Wikidata, the default of London when no place is supplied, pricing ($0.002/call, first 25 free, failed calls free), and that repeats cost money. This is exactly the kind of operational context annotations cannot carry.

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?

Purpose and data are front-loaded, followed by fields, sources, usage, example, and pricing in a logical order. The long run-on sentences and a couple of filler clauses ('any agent that needs the weather') cost some tightness.

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?

With no output schema, the description carries the return-value burden and does so by listing temperature, conditions, precipitation, wind, humidity, cloud cover, pressure, and the hourly series. Units are only stated for temperature (Celsius) and precipitation (mm), leaving wind and pressure units unspecified.

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 both the city-vs-coordinates choice and the 1-48 hour range are already documented. The description adds only a usage example (city=London) and the note that 48 hours covers tomorrow, so the baseline of 3 applies.

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?

The description gives a specific verb+resource (current weather plus 48-hour hourly forecast) with explicit lookup modes (city name or lat/lon) and enumerates the returned fields, so an agent can distinguish it from siblings like air_quality or airport_status without opening the schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It names concrete usage contexts (travel and event planning, logistics, agriculture) and gives an example call, which clarifies intent. It stops short of exclusions or naming alternatives, so there is no explicit when-not guidance.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.