Skip to main content
Glama

wsdot-mcp-server

by io.github.cyanheads
OverviewDiscussionsAdmin

Search Highway Alerts

wsdot_search_alerts
Read-only

Returns active WA highway alerts: incidents, construction, closures, and restrictions. Filter by state route ("I-90", "90", "SR 520", or "520" all work), WSDOT region (Northwest, Olympic, Southwest, South Central, North Central, Eastern), or milepost range, matched against the alert's full extent. Omit all filters to return all current statewide alerts. Results are ordered by alertId and paged — pass offset/limit to page through the full set (the notice reports the next offset).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMaximum alerts to return in this page (1–500). Defaults to 50.
offsetNoZero-based index of the first alert to return, for paging. Defaults to 0.
regionNoWSDOT region name as it appears in alert data: "Northwest", "Olympic", "Southwest", "South Central", "North Central", or "Eastern". Matching is case-insensitive.
stateRouteNoState route to filter by. Accepts natural forms — "I-90", "90", "090", "SR 520", "520" — matched case- and space-insensitively to the route number. A route-type prefix is compared only when both sides carry one, so "SR 26" never matches US 26 while a bare "26" matches either. Omit to include all routes.
endMilepostNoEnd of the milepost range. Matched by extent overlap like startMilepost, so an alert beginning inside the range and continuing past it is returned.
startMilepostNoStart of the milepost range. An alert matches when its extent overlaps the range, so a closure running from MP 10 to MP 30 is returned for a range starting at MP 20. Either bound may be given alone. Alerts reporting no milepost are always included.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
errorNoPresent when the call failed. Absent on success.
alertsNoMatching highway alerts.
noticeNoInformational note about the page window, or guidance when no alerts matched the filters or the offset ran past the end.
hasMoreNoTrue when more alerts remain beyond the current page.
nextOffsetNoOffset to pass to retrieve the next page, or null when this is the last page.
totalCountNoTotal alerts matching the filters across all pages (not just this page).
appliedFiltersNoActive filters applied to the alert search.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • removedOutput schema / properties / nextOffset / anyOf
      Removed value: -[
-  {
-    "type": "number"
-  },
-  {
-    "type": "null"
-  }
-]
    • addedOutput schema / properties / nextOffset / type
      Added value: +[
+  "number",
+  "null"
+]
  2. 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": [
+      "alerts",
+      "totalCount",
+      "nextOffset",
+      "hasMore",
+      "appliedFilters"
+    ]
+  },
+  {
+    "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: `api_unavailable`: WSDOT Traffic API is unreachable or returns a non-2xx response after retries. `invalid_access_code`: WSDOT rejected the request because WSDOT_ACCESS_CODE is missing, invalid, or not registered. Other values are possible when a failure originates below the handler.",
+          "examples": [
+            "api_unavailable",
+            "invalid_access_code"
+          ],
+          "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: -[
-  "alerts",
-  "totalCount",
-  "nextOffset",
-  "hasMore",
-  "appliedFilters"
-]
  3. Changed7 schema fields changed
    • addedInput schema / properties / limit
      Added value: +{
+  "description": "Maximum alerts to return in this page (1–500). Defaults to 50.",
+  "maximum": 500,
+  "minimum": 1,
+  "type": "integer"
+}
    • addedInput schema / properties / offset
      Added value: +{
+  "description": "Zero-based index of the first alert to return, for paging. Defaults to 0.",
+  "maximum": 9007199254740991,
+  "minimum": 0,
+  "type": "integer"
+}
    • addedOutput schema / properties / hasMore
      Added value: +{
+  "description": "True when more alerts remain beyond the current page.",
+  "type": "boolean"
+}
    • addedOutput schema / properties / nextOffset
      Added value: +{
+  "anyOf": [
+    {
+      "type": "number"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "description": "Offset to pass to retrieve the next page, or null when this is the last page."
+}
    • changedOutput schema / properties / notice / description
      Previous value: -"Optional guidance when no alerts matched — suggests broadening or removing filters. Absent when results are returned."New value: +"Informational note about the page window, or guidance when no alerts matched the filters or the offset ran past the end."
    • changedOutput schema / properties / totalCount / description
      Previous value: -"Total number of alerts returned."New value: +"Total alerts matching the filters across all pages (not just this page)."
    • changedOutput schema / required
      Previous value: -[
-  "alerts",
-  "totalCount",
-  "appliedFilters"
-]New value: +[
+  "alerts",
+  "totalCount",
+  "nextOffset",
+  "hasMore",
+  "appliedFilters"
+]
  4. Changed2 schema fields changed
    • changedOutput schema / properties / alerts / items / properties / extendedDescription / description
      Previous value: -"Full description of the alert."New value: +"Full description of the alert, normalized to plain text on the same terms as headlineDescription. Often absent — most alerts carry only a headline."
    • changedOutput schema / properties / alerts / items / properties / headlineDescription / description
      Previous value: -"Short summary of the alert."New value: +"Short summary of the alert, as plain text. Upstream authors these in a rich-text editor, so any markup is normalized away and a link is rendered inline as \"link text (url)\"."
  5. Changed3 schema fields changed
    • changedInput schema / properties / endMilepost / description
      Previous value: -"End of milepost range to filter alerts."New value: +"End of the milepost range. Matched by extent overlap like startMilepost, so an alert beginning inside the range and continuing past it is returned."
    • changedInput schema / properties / startMilepost / description
      Previous value: -"Start of milepost range to filter alerts."New value: +"Start of the milepost range. An alert matches when its extent overlaps the range, so a closure running from MP 10 to MP 30 is returned for a range starting at MP 20. Either bound may be given alone. Alerts reporting no milepost are always included."
    • changedInput schema / properties / stateRoute / description
      Previous value: -"State route to filter by. Accepts natural forms — \"I-90\", \"90\", \"090\", \"SR 520\", \"520\" — matched case- and space-insensitively to the canonical WSDOT route number. Omit to include all routes."New value: +"State route to filter by. Accepts natural forms — \"I-90\", \"90\", \"090\", \"SR 520\", \"520\" — matched case- and space-insensitively to the route number. A route-type prefix is compared only when both sides carry one, so \"SR 26\" never matches US 26 while a bare \"26\" matches either. Omit to include all routes."
  6. Changed1 schema field changed
    • changedInput schema / properties / stateRoute / description
      Previous value: -"Zero-padded 3-digit state route number (e.g. \"005\" for I-5, \"090\" for I-90, \"520\" for SR 520)."New value: +"State route to filter by. Accepts natural forms — \"I-90\", \"90\", \"090\", \"SR 520\", \"520\" — matched case- and space-insensitively to the canonical WSDOT route number. Omit to include all routes."
  7. Changed5 schema fields changed
    • changedOutput schema / properties / alerts / items / properties / endRoadwayLocation / properties / direction / description
      Previous value: -"Travel direction."New value: +"Travel direction code: N/S/E/W, B (both directions), A (alternating); may appear as NB/SB/EB/WB."
    • changedOutput schema / properties / alerts / items / properties / endTime / description
      Previous value: -"When the event is expected to end."New value: +"When the event is expected to end (ISO 8601)."
    • changedOutput schema / properties / alerts / items / properties / lastUpdatedTime / description
      Previous value: -"When this alert was last updated."New value: +"When this alert was last updated (ISO 8601)."
    • changedOutput schema / properties / alerts / items / properties / startRoadwayLocation / properties / direction / description
      Previous value: -"Travel direction."New value: +"Travel direction code: N/S/E/W, B (both directions), A (alternating); may appear as NB/SB/EB/WB."
    • changedOutput schema / properties / alerts / items / properties / startTime / description
      Previous value: -"When the event started or is scheduled to start."New value: +"When the event started or is scheduled to start (ISO 8601)."
  8. Changed1 schema field changed
    • changedInput schema / properties / region / description
      Previous value: -"WSDOT region name: Northwest, Olympic, Southwest, South Central, North Central, or Eastern."New value: +"WSDOT region name as it appears in alert data: \"Northwest\", \"Olympic\", \"Southwest\", \"South Central\", \"North Central\", or \"Eastern\". Matching is case-insensitive."
  9. Changed3 schema fields changed
    • addedOutput schema / properties / appliedFilters
      Added value: +{
+  "additionalProperties": false,
+  "description": "Active filters applied to the alert search.",
+  "properties": {
+    "endMilepost": {
+      "description": "End milepost filter applied.",
+      "type": "number"
+    },
+    "region": {
+      "description": "Region filter applied.",
+      "type": "string"
+    },
+    "startMilepost": {
+      "description": "Start milepost filter applied.",
+      "type": "number"
+    },
+    "stateRoute": {
+      "description": "State route filter applied.",
+      "type": "string"
+    }
+  },
+  "type": "object"
+}
    • addedOutput schema / properties / notice
      Added value: +{
+  "description": "Optional guidance when no alerts matched — suggests broadening or removing filters. Absent when results are returned.",
+  "type": "string"
+}
    • changedOutput schema / required
      Previous value: -[
-  "alerts",
-  "totalCount"
-]New value: +[
+  "alerts",
+  "totalCount",
+  "appliedFilters"
+]
  10. First observed

TDQS

A4.7/5.0
Behavior5/5

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

It discloses useful runtime behavior beyond the readOnlyHint annotation: results are ordered by alertId, paged with a reported next offset, and filters match against the alert's full extent. This aligns with the annotation and adds real operational context.

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?

Three dense, well-ordered sentences cover purpose, filtering, statewide behavior, ordering, and pagination without filler or redundant schema repetition.

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?

With an output schema present, the description does not need to narrate the return shape. It covers selection, filtering, optionality, ordering, and pagination, giving an agent everything needed to invoke the tool correctly.

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?

The input schema already documents all six parameters thoroughly, so the baseline is 3. The description adds tool-level meaning: filters are optional, matching uses the full alert extent, and offset/limit drive pagination across the statewide set.

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 opens with a specific verb and resource: 'Returns active WA highway alerts: incidents, construction, closures, and restrictions.' It clearly distinguishes this tool from the ferry, mountain pass, camera, and border wait sibling tools.

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 gives concrete usage patterns: filter by route, region, or milepost; omit all filters for a statewide list; and use offset/limit for paging. It does not explicitly name an alternative tool, but no sibling overlaps with this alert-searching function.

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

All wsdot-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