Skip to main content
Glama

Nws

by io.github.pipeworx-io

Get Alerts

get_alerts
Read-onlyIdempotent

Active NWS watches / warnings / advisories. Filter by US state (2-letter code), point (lat,lon), severity, or status. Returns event name, severity, urgency, headline, description, affected areas, and effective/expires times.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
areaNo2-letter US state/territory code (e.g., "CA", "TX")
eventNoRestrict to a specific event type (e.g., "Tornado Warning")
limitNoCap alerts returned (default 50, max 500)
urgencyNoImmediate | Expected | Future | Past | Unknown
latitudeNoLatitude (use with longitude for point query)
severityNoExtreme | Severe | Moderate | Minor | Unknown
longitudeNoLongitude (use with latitude for point query)

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
countYesTotal number of alerts returned
alertsYes

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: +[
+  {
+    "area": "TX"
+  },
+  {
+    "latitude": 40.7128,
+    "longitude": -74.006,
+    "severity": "Severe",
+    "urgency": "Immediate"
+  },
+  {
+    "event": "Tornado Warning",
+    "limit": 20
+  }
+]
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "alerts": {
+      "items": {
+        "properties": {
+          "area": {
+            "description": "Affected area description",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "category": {
+            "description": "Alert category",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "certainty": {
+            "description": "Certainty level",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "description": {
+            "description": "Full alert description",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "effective": {
+            "description": "Effective time ISO 8601",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "ends": {
+            "description": "End time ISO 8601",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "event": {
+            "description": "Event type (e.g. Tornado Warning)",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "expires": {
+            "description": "Expiration time ISO 8601",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "headline": {
+            "description": "Alert headline",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "id": {
+            "description": "Alert identifier",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "instruction": {
+            "description": "Safety instructions",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "onset": {
+            "description": "Onset time ISO 8601",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "response": {
+            "description": "Recommended response type",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "sender": {
+            "description": "Issuing organization",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "sent": {
+            "description": "Sent time ISO 8601",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "severity": {
+            "description": "Extreme/Severe/Moderate/Minor",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "status": {
+            "description": "Alert status",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "urgency": {
+            "description": "Immediate/Expected/Future/Past",
+            "type": [
+              "string",
+              "null"
+            ]
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "count": {
+      "description": "Total number of alerts returned",
+      "type": "number"
+    }
+  },
+  "required": [
+    "count",
+    "alerts"
+  ],
+  "type": "object"
+}
  2. First observed

TDQS

A3.6/5.0
Behavior4/5

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

Describes return fields (event name, severity, etc.) and filter options, adding value beyond annotations which already declare readOnlyHint, idempotentHint, etc. No contradictions.

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, front-loaded with resource and then filters/return fields. No superfluous text.

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?

Covers main purpose, filtering, and return values. With output schema and annotations, only minor missing details like pagination (though limit param is in schema).

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 has 100% coverage, so description is not required to add much. Description summarizes filters but does not add new parameter-specific details beyond schema.

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?

Description clearly states it retrieves active NWS watches/warnings/advisories, with filtering options and return fields. However, it does not explicitly differentiate from sibling tool 'recent_alerts'.

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?

No guidance on when to use this tool vs alternatives like 'recent_alerts'. Only lists available filters but no context on when they are appropriate.

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