Skip to main content
Glama

US weather forecast and active alerts (NWS)

geo_weather
Read-only

Weather forecast and active alerts for a US address or lat/lon point: NWS office, grid, forecast and county zones, time zone; 7-day periods (temperature, wind, precipitation chance, short and detailed forecast) or, with hourly=true, the next 24 hours adding humidity and dew point; active watches, warnings and advisories with event, severity, urgency, certainty, headline, timing and area. Sources: NOAA National Weather Service API, US Census Geocoder for addresses. Price: $0.005 per successful call, paid in USDC with x402 v2; failed calls and calls that match nothing are not charged.

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

Input Schema

NameRequiredDescriptionDefault
latNoLatitude in decimal degrees, paired with lon; rounded to 4 decimals. Points outside NWS forecast coverage (US states and territories, land) return 404.
lonNoLongitude in decimal degrees, paired with lat; rounded to 4 decimals.
hourlyNotrue returns the next 24 hourly periods (with humidity and dew point) instead of the 7-day day/night periods. Default false.
addressNoOne-line US street address (5 to 100 characters), geocoded with the Census Geocoder. Mutually exclusive with lat/lon.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • changedInput schema / properties / address / examples
      Previous value: -[
      -  "4201 St Antoine St, Detroit, MI 48201"
      -]New value: +[
      +  "350 5th Ave, New York, NY 10118"
      +]
    • changedInput schema / properties / lat / examples
      Previous value: -[
      -  "42.354"
      -]New value: +[
      +  "40.7479"
      +]
    • changedInput schema / properties / lon / examples
      Previous value: -[
      -  "-83.0535"
      -]New value: +[
      +  "-73.9851"
      +]
  2. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so safety is covered. The description adds meaningful operational context beyond that: upstream data sources (NWS API, Census Geocoder), 404 for points outside NWS coverage, and a precise billing model ($0.005 per successful call, USDC via x402 v2, no charge on failure or empty matches). It does not discuss rate limits or latency, but the cost/auth model disclosure is substantive.

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 the core purpose, then branches by mode, then sources and pricing; semicolon-delimited clauses keep it scannable with no filler sentences. It is on the dense side, and the pricing/source clause could be trimmed without losing actionable information.

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?

There is no output schema, so the description carries the burden of describing return values, and it does: forecast period fields, alert fields (event, severity, urgency, certainty, headline, timing, area), plus the auxiliary NWS office/grid/zone/time-zone data. Combined with the annotation-covered safety profile and full schema coverage, an agent has what it needs; only pagination/response-size behavior is unaddressed.

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 description coverage is 100%, so the schema already documents lat, lon, hourly and address, establishing a baseline of 3. The description adds value by explaining what the hourly flag changes in the result (24 hours with humidity and dew point versus 7-day day/night periods) and by naming the geocoder behind address resolution, though it does not restate the mutual exclusivity or rounding rules that live in the schema.

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+resource pair (forecast and active alerts) plus the exact geographic input modes (US address or lat/lon) and the payload contents: NWS office, grid, zones, time zone, 7-day periods, hourly option, alerts. An agent can distinguish this from geo_us_address, which only geocodes, without opening either 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?

Clear context for when this applies: US locations only, address or lat/lon, and the hourly=true switch changes the time resolution. It does not name a sibling alternative or spell out when-not to call it (e.g., non-US locations, or using geo_us_address for pure geocoding), so it stops short of explicit routing 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.

Resources