Global Weather (MET Norway)

weather_forecast

Get current weather and a 7-day forecast for any city or coordinate before travel, logistics, events or field work. Returns current temperature, wind, humidity, pressure, cloud and precipitation, a 24-hour hourly outlook and daily min/max with precipitation, from the Norwegian Meteorological Institute's global model; city names are resolved via GeoNames (30k+ cities). Use when a plan depends on the weather in the coming days. $0.006 per call, USDC on Base (x402).

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_forecast"
  }
}

Input Schema

Name	Required	Description
`lat`	No	Latitude
`lon`	No	Longitude
`city`	No	City name
`days`	No	Days (default 7)
`country`	No	ISO2 country
`payment_signature`	No	x402 v2 PAYMENT-SIGNATURE header value. Omit to receive payment requirements.

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 16, 2026

TDQS

A4.1/5.0

Behavior4/5

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

With no annotations, the description carries the full burden and does well: it discloses the data sources (MET Norway global model, GeoNames 30k+ cities), the return contents, and crucially the cost and payment mechanism ($0.006/call, USDC on Base via x402). It omits rate limits and error/failure behavior, so not a 5.

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?

Front-loaded with purpose and return contents, then usage and pricing. The enumerated return fields are somewhat list-heavy but each clause carries information; no filler sentences.

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 exists, so the description must describe returns, and it does thoroughly (current conditions, 24-hour hourly outlook, daily min/max with precipitation). Payment flow and data sources are covered; only failure modes and limits are missing.

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 the schema already documents all six parameters, giving a baseline of 3. The description adds only marginal meaning ('any city or coordinate' implies city vs lat/lon; '7-day' aligns with the days default) and does not explain the days max of 9, country, or payment_signature.

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?

States a specific verb (Get) and resource (current weather and a 7-day forecast) with scope ('any city or coordinate'). An agent immediately knows what it retrieves; no siblings exist to distinguish from, but the purpose is unambiguous.

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?

Gives clear usage context ('before travel, logistics, events or field work') and a selection condition ('Use when a plan depends on the weather in the coming days'). It does not name alternatives or state when-not to use it, so it stops short of a 5.

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

All Global Weather (MET Norway) tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?