Skip to main content
Glama

Nws

by io.github.pipeworx-io

Get Hourly Forecast

get_hourly_forecast
Read-onlyIdempotent

Get the hourly NWS forecast for a US lat/lon (~168 hours). Useful for short-term planning, severe-weather windows, or precipitation timing.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
latitudeYesUS latitude
longitudeYesUS longitude
max_hoursNoCap hours returned (default 24)

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
periodsYes
updatedNoForecast update timestamp
locationYes
period_countYesNumber of forecast hours

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed2 schema fields changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "latitude": 40.7128,
+    "longitude": -74.006
+  },
+  {
+    "latitude": 39.7392,
+    "longitude": -104.9903,
+    "max_hours": 48
+  }
+]
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "location": {
+      "properties": {
+        "city": {
+          "description": "Nearest city name",
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "grid": {
+          "description": "NWS grid ID and coordinates",
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "latitude": {
+          "description": "Input latitude",
+          "type": "number"
+        },
+        "longitude": {
+          "description": "Input longitude",
+          "type": "number"
+        },
+        "radar_station": {
+          "description": "Nearest radar station",
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "state": {
+          "description": "State abbreviation",
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "timezone": {
+          "description": "IANA timezone",
+          "type": [
+            "string",
+            "null"
+          ]
+        }
+      },
+      "required": [
+        "latitude",
+        "longitude"
+      ],
+      "type": "object"
+    },
+    "period_count": {
+      "description": "Number of forecast hours",
+      "type": "number"
+    },
+    "periods": {
+      "items": {
+        "properties": {
+          "detailed": {
+            "description": "Detailed forecast text",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "end": {
+            "description": "End time ISO 8601",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "is_daytime": {
+            "description": "Daytime period flag",
+            "type": [
+              "boolean",
+              "null"
+            ]
+          },
+          "name": {
+            "description": "Period name (e.g. Tonight)",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "precip_chance_pct": {
+            "description": "Precipitation probability",
+            "type": [
+              "number",
+              "null"
+            ]
+          },
+          "short": {
+            "description": "Short forecast text",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "start": {
+            "description": "Start time ISO 8601",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "temperature": {
+            "description": "Temperature in unit",
+            "type": [
+              "number",
+              "null"
+            ]
+          },
+          "temperature_unit": {
+            "description": "F or C",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "wind": {
+            "description": "Wind speed and direction",
+            "type": [
+              "string",
+              "null"
+            ]
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "updated": {
+      "description": "Forecast update timestamp",
+      "type": [
+        "string",
+        "null"
+      ]
+    }
+  },
+  "required": [
+    "location",
+    "period_count",
+    "periods"
+  ],
+  "type": "object"
+}
  2. First observed

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, covering safety. The description adds the source (NWS) and duration (~168 hours) but does not disclose behavioral traits beyond annotations. No contradiction.

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 sentences, no filler. First sentence states the core functionality; second sentence lists use cases. Every word adds value. Ideal length for a simple tool.

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?

Given the simple parameters, full schema coverage, output schema present, and annotations, the description is largely complete. However, it does not clarify how this differs from sibling 'get_forecast', which could be a gap for agents choosing between similar tools.

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 coverage is 100% with descriptions for all parameters. The description adds no extra meaning beyond the schema; it lists use cases but does not elaborate on parameter values or constraints. Baseline 3 is appropriate.

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?

The description clearly states the tool retrieves hourly NWS forecasts for US lat/lon up to ~168 hours. It uses a specific verb (Get) and identifies the resource (hourly NWS forecast). It does not explicitly distinguish from sibling tool 'get_forecast', but the hourly aspect is clear from title and description.

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?

The description provides explicit use cases: 'short-term planning, severe-weather windows, or precipitation timing.' This helps agents decide when to use it. It does not mention when to avoid or alternatives, but the context is sufficient for typical scenarios.

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

All Nws toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.7/5.0
Disambiguation2/5

Many tools have overlapping purposes, e.g., multiple Polymarket analysis tools, several query tools (ask_pipeworx, deep_research, compare_entities, entity_profile) with unclear boundaries. Agents may struggle to choose the correct tool.

Naming Consistency3/5

While most names use snake_case, there is no consistent prefix pattern across subdomains (e.g., 'ask_', 'get_', 'polymarket_', 'pipeworx_'). Some names like 'bet_research' and 'deep_research' follow different conventions within the same domain.

Tool Count2/5

34 tools is excessive for a server named 'Nws' that primarily suggests weather. The set covers many unrelated domains (prediction markets, npm scanning, memory), making the scope unfocused and overloaded.

Completeness3/5

The server has decent coverage for prediction markets and company financials, but weather tools are limited to basic forecasts/alerts, lacking radar, climate, or historical data. Other domains like npm scanning seem tacked on.

Resources