Skip to main content
Glama

nws-weather-mcp-server

by io.github.cyanheads
OverviewDiscussionsAdmin

Nws Find Stations

nws_find_stations
Read-only

Find weather observation stations near a location. Returns stations sorted by proximity with distance and bearing. Use to discover station IDs for nws_get_observations.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMax stations per page (1-50). totalCount still reports every station near the point, so pass the returned nextCursor as cursor to reach the rest.
cursorNoOpaque continuation token from a previous response's nextCursor. Omit for the first page. The token carries its own page size, so limit applies to the first page only. Every call re-fetches the station list, so pages are contiguous within one response; the registry changes rarely, but a later call can window an updated list.
latitudeYesCenter latitude for proximity search.
longitudeYesCenter longitude for proximity search.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
errorNoPresent when the call failed. Absent on success.
shownNoNumber of stations returned in this page
noticeNoGuidance when no stations were found near the requested coordinates, when stations remain beyond this page, or when the supplied cursor points past the end of the list.
stationsNoNearby stations sorted by distance
nextCursorNoOpaque token for the next page of stations — pass it back as `cursor`. Omitted when this is the last page.
totalCountNoTotal observation stations available near this location before the page limit was applied — NOT the number returned in this page, which is shown. Same value on every page of one query; compare it against shown to tell whether stations were withheld.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / properties / error / properties / data / properties / reason / description
      Previous value: -"Machine-readable failure mode. Declared by this tool: `out_of_scope`: Coordinates fall outside US National Weather Service coverage Other values are possible when a failure originates below the handler."New value: +"Machine-readable failure mode. Declared by this tool: `out_of_scope`: Coordinates fall outside US National Weather Service coverage. Other values are possible when a failure originates below the handler."
  2. Changed2 schema fields changed
    • removedOutput schema / properties / stations / items / properties / elevationM / anyOf
      Removed value: -[
-  {
-    "type": "number"
-  },
-  {
-    "type": "null"
-  }
-]
    • addedOutput schema / properties / stations / items / properties / elevationM / type
      Added value: +[
+  "number",
+  "null"
+]
  3. Changed6 schema fields changed
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
    • addedInput schema / additionalProperties
      Added value: +false
    • changedOutput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
    • addedOutput schema / anyOf
      Added value: +[
+  {
+    "not": {
+      "required": [
+        "error"
+      ]
+    },
+    "required": [
+      "stations",
+      "totalCount",
+      "shown"
+    ]
+  },
+  {
+    "required": [
+      "error"
+    ]
+  }
+]
    • addedOutput schema / properties / error
      Added value: +{
+  "additionalProperties": {},
+  "description": "Present when the call failed. Absent on success.",
+  "properties": {
+    "code": {
+      "description": "JSON-RPC error code for this failure.",
+      "maximum": 9007199254740991,
+      "minimum": -9007199254740991,
+      "type": "integer"
+    },
+    "data": {
+      "additionalProperties": {},
+      "properties": {
+        "reason": {
+          "description": "Machine-readable failure mode. Declared by this tool: `out_of_scope`: Coordinates fall outside US National Weather Service coverage Other values are possible when a failure originates below the handler.",
+          "examples": [
+            "out_of_scope"
+          ],
+          "type": "string"
+        },
+        "recovery": {
+          "additionalProperties": {},
+          "description": "Actionable next step for the caller.",
+          "properties": {
+            "hint": {
+              "type": "string"
+            }
+          },
+          "required": [
+            "hint"
+          ],
+          "type": "object"
+        },
+        "retryable": {
+          "description": "Whether retrying may succeed.",
+          "type": "boolean"
+        }
+      },
+      "type": "object"
+    },
+    "message": {
+      "description": "Human-readable description of what went wrong.",
+      "type": "string"
+    }
+  },
+  "required": [
+    "code",
+    "message"
+  ],
+  "type": "object"
+}
    • removedOutput schema / required
      Removed value: -[
-  "stations",
-  "totalCount",
-  "shown"
-]
  4. Changed5 schema fields changed
    • changedInput schema / properties / limit / description
      Previous value: -"Max stations per page (1-50). totalFound still reports every station near the point, so pass the returned nextCursor as cursor to reach the rest."New value: +"Max stations per page (1-50). totalCount still reports every station near the point, so pass the returned nextCursor as cursor to reach the rest."
    • addedOutput schema / properties / shown
      Added value: +{
+  "description": "Number of stations returned in this page",
+  "type": "number"
+}
    • changedOutput schema / properties / totalCount / description
      Previous value: -"Number of stations returned in this page"New value: +"Total observation stations available near this location before the page limit was applied — NOT the number returned in this page, which is shown. Same value on every page of one query; compare it against shown to tell whether stations were withheld."
    • removedOutput schema / properties / totalFound
      Removed value: -{
-  "description": "Total observation stations available near this location before the page limit was applied. Same value on every page of one query.",
-  "type": "number"
-}
    • changedOutput schema / required
      Previous value: -[
-  "stations",
-  "totalFound",
-  "totalCount"
-]New value: +[
+  "stations",
+  "totalCount",
+  "shown"
+]
  5. Changed6 schema fields changed
    • addedInput schema / properties / cursor
      Added value: +{
+  "description": "Opaque continuation token from a previous response's nextCursor. Omit for the first page. The token carries its own page size, so limit applies to the first page only. Every call re-fetches the station list, so pages are contiguous within one response; the registry changes rarely, but a later call can window an updated list.",
+  "type": "string"
+}
    • changedInput schema / properties / limit / description
      Previous value: -"Max stations to return (1-50)."New value: +"Max stations per page (1-50). totalFound still reports every station near the point, so pass the returned nextCursor as cursor to reach the rest."
    • addedOutput schema / properties / nextCursor
      Added value: +{
+  "description": "Opaque token for the next page of stations — pass it back as `cursor`. Omitted when this is the last page.",
+  "type": "string"
+}
    • changedOutput schema / properties / notice / description
      Previous value: -"Guidance when no stations were found near the requested coordinates."New value: +"Guidance when no stations were found near the requested coordinates, when stations remain beyond this page, or when the supplied cursor points past the end of the list."
    • changedOutput schema / properties / totalCount / description
      Previous value: -"Number of stations returned (respects the limit parameter)"New value: +"Number of stations returned in this page"
    • changedOutput schema / properties / totalFound / description
      Previous value: -"Total observation stations available near this location before the limit was applied"New value: +"Total observation stations available near this location before the page limit was applied. Same value on every page of one query."
  6. Changed4 schema fields changed
    • addedOutput schema / properties / notice
      Added value: +{
+  "description": "Guidance when no stations were found near the requested coordinates.",
+  "type": "string"
+}
    • addedOutput schema / properties / totalCount
      Added value: +{
+  "description": "Number of stations returned (respects the limit parameter)",
+  "type": "number"
+}
    • addedOutput schema / properties / totalFound
      Added value: +{
+  "description": "Total observation stations available near this location before the limit was applied",
+  "type": "number"
+}
    • changedOutput schema / required
      Previous value: -[
-  "stations"
-]New value: +[
+  "stations",
+  "totalFound",
+  "totalCount"
+]
  7. Changed5 schema fields changed
    • removedOutput schema / properties / stations / items / properties / distance
      Removed value: -{
-  "description": "Distance from query point in km",
-  "type": "number"
-}
    • addedOutput schema / properties / stations / items / properties / distanceKm
      Added value: +{
+  "description": "Distance from query point in kilometers",
+  "type": "number"
+}
    • removedOutput schema / properties / stations / items / properties / elevation
      Removed value: -{
-  "anyOf": [
-    {
-      "type": "number"
-    },
-    {
-      "type": "null"
-    }
-  ],
-  "description": "Elevation in meters"
-}
    • addedOutput schema / properties / stations / items / properties / elevationM
      Added value: +{
+  "anyOf": [
+    {
+      "type": "number"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "description": "Elevation in meters"
+}
    • changedOutput schema / properties / stations / items / required
      Previous value: -[
-  "stationId",
-  "name",
-  "distance",
-  "bearing",
-  "elevation",
-  "timeZone",
-  "county",
-  "forecastZone"
-]New value: +[
+  "stationId",
+  "name",
+  "distanceKm",
+  "bearing",
+  "elevationM",
+  "timeZone",
+  "county",
+  "forecastZone"
+]
  8. Changed1 schema field changed
    • addedOutput schema / properties / stations / items / description
      Added value: +"Observation station record with identity, location, and zone codes"
  9. First observed

TDQS

A4.3/5.0
Behavior4/5

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

The readOnlyHint annotation already communicates safety, and the description adds meaningful behavioral detail: stations are returned sorted by proximity and include distance and bearing. This is useful beyond the annotation, though it does not discuss error conditions or rate limits.

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 with no filler: the core function, the output behavior, and the intended use case are all front-loaded. Every sentence earns its place.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The tool is simple, annotations cover the read-only nature, the input schema is fully descriptive, and an output schema exists. The description provides the one missing piece—why an agent would call this tool and what it returns—making it complete for selection and invocation.

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 fully documents latitude, longitude, limit, and cursor. The description adds no parameter-specific semantics beyond 'near a location', which maps to latitude/longitude but does not exceed what the schema provides.

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 uses a specific verb ('Find') with a clear resource ('weather observation stations near a location') and clearly identifies the downstream purpose: discovering station IDs for nws_get_observations. This distinguishes it from the sibling forecast, alert, and discussion tools without ambiguity.

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 explicitly states when this tool should be used: to discover station IDs for nws_get_observations. It does not list exclusions or alternative tools, but the discovery role is clear and sufficient for this simple tool.

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

All nws-weather-mcp-server toolsInspect
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