Skip to main content
Glama

wsdot-mcp-server

by io.github.cyanheads
OverviewDiscussionsAdmin

Get Mountain Pass Conditions

wsdot_get_mountain_passes
Read-only

Returns current road conditions for all Washington State mountain passes: status, weather, road condition, traction laws, temperature, and elevation. Includes all 16 passes (Snoqualmie, Stevens, White, Blewett, Cayuse, etc.). Use for "is the pass open?", traction law status, or winter driving planning.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
errorNoPresent when the call failed. Absent on success.
noticeNoOptional notice when no pass data is available — e.g. API temporarily unavailable. Absent on normal results.
passesNoAll WA mountain pass conditions.
totalCountNoTotal number of passes returned.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • changedOutput schema / properties / passes / items / properties / mountainPassId / description
      Previous value: -"Numeric identifier for the pass."New value: +"Numeric identifier for the pass. Absent when upstream omits it."
    • changedOutput schema / properties / passes / items / properties / mountainPassName / description
      Previous value: -"Human-readable pass name (e.g. \"Snoqualmie Pass\")."New value: +"Human-readable pass name (e.g. \"Snoqualmie Pass\"). Absent when upstream omits it."
    • removedOutput schema / properties / passes / items / required
      Removed value: -[
-  "mountainPassId",
-  "mountainPassName"
-]
  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": [
+      "passes",
+      "totalCount"
+    ]
+  },
+  {
+    "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: -[
-  "passes",
-  "totalCount"
-]
  3. Changed11 schema fields changed
    • changedOutput schema / properties / passes / items / properties / dateUpdated / description
      Previous value: -"Timestamp of the last condition update."New value: +"Timestamp of the last condition update (ISO 8601)."
    • changedOutput schema / properties / passes / items / properties / restrictionOne / description
      Previous value: -"Primary travel restriction, if any."New value: +"Primary travel/traction restriction (typically one direction of travel)."
    • removedOutput schema / properties / passes / items / properties / restrictionOne / properties / comment
      Removed value: -{
-  "description": "Restriction description (e.g. \"Traction Tires Required\").",
-  "type": "string"
-}
    • addedOutput schema / properties / passes / items / properties / restrictionOne / properties / text
      Added value: +{
+  "description": "Restriction / traction-law text (e.g. \"Traction Tires Required, Chains Required (Except All Wheel Drive)\"). Reads \"No current information available\" or \"No restrictions\" when nothing is in effect.",
+  "type": "string"
+}
    • addedOutput schema / properties / passes / items / properties / restrictionOne / properties / travelDirection
      Added value: +{
+  "description": "Direction this restriction applies to (e.g. \"Northbound\", \"Eastbound\", \"Both directions\").",
+  "type": "string"
+}
    • removedOutput schema / properties / passes / items / properties / restrictionOne / properties / type
      Removed value: -{
-  "description": "Restriction type code.",
-  "type": "string"
-}
    • changedOutput schema / properties / passes / items / properties / restrictionTwo / description
      Previous value: -"Secondary travel restriction, if any."New value: +"Secondary travel/traction restriction (typically the opposite direction)."
    • removedOutput schema / properties / passes / items / properties / restrictionTwo / properties / comment
      Removed value: -{
-  "description": "Restriction description.",
-  "type": "string"
-}
    • addedOutput schema / properties / passes / items / properties / restrictionTwo / properties / text
      Added value: +{
+  "description": "Restriction / traction-law text for the second direction.",
+  "type": "string"
+}
    • addedOutput schema / properties / passes / items / properties / restrictionTwo / properties / travelDirection
      Added value: +{
+  "description": "Direction this restriction applies to (e.g. \"Southbound\", \"Westbound\").",
+  "type": "string"
+}
    • removedOutput schema / properties / passes / items / properties / restrictionTwo / properties / type
      Removed value: -{
-  "description": "Restriction type code.",
-  "type": "string"
-}
  4. Changed3 schema fields changed
    • addedOutput schema / properties / notice
      Added value: +{
+  "description": "Optional notice when no pass data is available — e.g. API temporarily unavailable. Absent on normal results.",
+  "type": "string"
+}
    • addedOutput schema / properties / totalCount
      Added value: +{
+  "description": "Total number of passes returned.",
+  "type": "number"
+}
    • changedOutput schema / required
      Previous value: -[
-  "passes"
-]New value: +[
+  "passes",
+  "totalCount"
+]
  5. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations carry readOnlyHint=true, so the read-only nature is already declared. The description adds context by specifying the full scope (all 16 passes) and the fields returned, which goes beyond the annotation. No contradictions and no additional behavioral caveats are needed for a simple read-only fetch.

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 focused sentences: the first states the operation and output fields, the second offers practical usage examples. The core action and scope are front-loaded, with no filler or redundant phrasing. 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 has no parameters and no output schema concerns (it exists), and annotations cover safety. The description tells an agent what data it will receive, that it covers all passes, and when to use it. Nothing needed for correct selection or invocation is missing.

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 tool takes zero parameters, so the schema already fully defines the input (empty). Per rubric, 0 params baseline is 4. The description adds no parameter information, but none is required because there are no parameters to document.

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 clearly states a specific verb and resource: 'Returns current road conditions for all Washington State mountain passes.' It lists the data fields (status, weather, traction laws, etc.) and names example passes, making it unambiguous and distinguishable from sibling tools such as ferry alerts or travel times.

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 second sentence explicitly gives use cases: 'Use for "is the pass open?", traction law status, or winter driving planning.' This is clear context, though it does not name alternatives or state exclusions. Since the sibling tools are topically distinct, this is sufficient.

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