wsdot-mcp-server

Get Travel Times

wsdot_get_travel_times

Read-only

Returns current vs. average travel times for named WA highway corridors (I-5, I-90, SR 520, SR 99, I-405, SR 167, etc.). Use for "how congested is I-5?" or commute time estimates. The route filter matches two ways: a route designation ("I-5", "5", "SR 520") returns every corridor measured on that route, and any text also matches corridor names ("Everett"). When current time exceeds average, the corridor is congested. Results are paged — pass offset/limit to page through the full set. A page ends at limit or at a 24,000-byte response budget, whichever comes first; the notice reports the next offset.

Input Schema

TableJSON Schema

Name	Required	Description
`limit`	No	Maximum corridors to return in this page (1–500). Defaults to 50. A large page ends sooner, at the 24,000-byte response budget.
`route`	No	Optional filter. A route designation — "I-5", "5", "005", "SR 520", "520" — matches every corridor whose start or end point is on that route, whichever form the feed reports. Any text also matches the corridor name as a case-insensitive substring, so "Everett" finds the Seattle-Everett corridors. Omit to return all corridors.
`offset`	No	Zero-based index of the first corridor to return, for paging. Defaults to 0.

Output Schema

TableJSON Schema

Name	Required	Description
`error`	No	Present when the call failed. Absent on success.
`notice`	No	Informational note about the page window, or guidance when no corridors matched the route filter or the offset ran past the end.
`hasMore`	No	True when more corridors remain beyond the current page.
`corridors`	No	Travel time corridors matching the filter.
`nextOffset`	No	Offset to pass to retrieve the next page, or null when this is the last page.
`totalCount`	No	Total corridors matching the filter across all pages (not just this page).
`routeFilter`	No	The route name filter applied (lowercased), or absent if no filter was used.

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedSep 24, 2026

changedInput schema / properties / limit / description

Previous value: -"Maximum corridors to return in this page (1–500). Defaults to 50."New value: +"Maximum corridors to return in this page (1–500). Defaults to 50. A large page ends sooner, at the 24,000-byte response budget."

addedInput schema / properties / route / maxLength
```
Added value: +200
```

Changed2 schema fields changedSep 20, 2026
- removedOutput schema / properties / nextOffset / anyOf
```
Removed value: -[
-  {
-    "type": "number"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / nextOffset / type
```
Added value: +[
+  "number",
+  "null"
+]
```

Changed6 schema fields changedAug 25, 2026

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": [
+      "corridors",
+      "totalCount",
+      "nextOffset",
+      "hasMore"
+    ]
+  },
+  {
+    "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: -[
-  "corridors",
-  "totalCount",
-  "nextOffset",
-  "hasMore"
-]

Changed7 schema fields changedJul 31, 2026

addedInput schema / properties / limit

Added value: +{
+  "description": "Maximum corridors 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 corridor to return, for paging. Defaults to 0.",
+  "maximum": 9007199254740991,
+  "minimum": 0,
+  "type": "integer"
+}

addedOutput schema / properties / hasMore

Added value: +{
+  "description": "True when more corridors 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 corridors matched the route filter. Absent when results are returned."New value: +"Informational note about the page window, or guidance when no corridors matched the route filter or the offset ran past the end."

changedOutput schema / properties / totalCount / description

Previous value: -"Total number of corridors returned."New value: +"Total corridors matching the filter across all pages (not just this page)."

changedOutput schema / required

Previous value: -[
-  "corridors",
-  "totalCount"
-]New value: +[
+  "corridors",
+  "totalCount",
+  "nextOffset",
+  "hasMore"
+]

Changed4 schema fields changedJul 31, 2026

changedInput schema / properties / route / description

Previous value: -"Optional text filter applied to corridor names (e.g. \"I-5\", \"SR 520\", \"I-405\"). Case-insensitive. Omit to return all corridors."New value: +"Optional filter. A route designation — \"I-5\", \"5\", \"005\", \"SR 520\", \"520\" — matches every corridor whose start or end point is on that route, whichever form the feed reports. Any text also matches the corridor name as a case-insensitive substring, so \"Everett\" finds the Seattle-Everett corridors. Omit to return all corridors."

changedOutput schema / properties / corridors / items / properties / averageTimeInMinutes / description

Previous value: -"Historical average travel time in minutes."New value: +"Historical average travel time in minutes. Absent when WSDOT reports no measurement for the corridor."

changedOutput schema / properties / corridors / items / properties / currentTimeInMinutes / description

Previous value: -"Current travel time in minutes."New value: +"Current travel time in minutes. Absent when WSDOT reports no measurement for the corridor — a reversible express lane closed in this direction reports none."

changedOutput schema / properties / corridors / items / properties / delayInMinutes / description

Previous value: -"Delay above average in minutes. Positive means congestion."New value: +"Delay above average in minutes. Positive means congestion. Absent when either travel time is unavailable."

Changed3 schema fields changedJun 9, 2026

changedOutput schema / properties / corridors / items / properties / endPoint / properties / direction / description

Previous value: -"Travel direction."New value: +"Travel direction code: N (north), S (south), E (east), W (west)."

changedOutput schema / properties / corridors / items / properties / startPoint / properties / direction / description

Previous value: -"Travel direction."New value: +"Travel direction code: N (north), S (south), E (east), W (west)."

changedOutput schema / properties / corridors / items / properties / timeUpdated / description

Previous value: -"When the travel time data was last updated."New value: +"When the travel time data was last updated (ISO 8601)."

Changed2 schema fields changedMay 30, 2026

addedOutput schema / properties / notice

Added value: +{
+  "description": "Optional guidance when no corridors matched the route filter. Absent when results are returned.",
+  "type": "string"
+}

addedOutput schema / properties / routeFilter

Added value: +{
+  "description": "The route name filter applied (lowercased), or absent if no filter was used.",
+  "type": "string"
+}

First observedMay 25, 2026

TDQS

A4.7/5.0

Behavior5/5

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

Annotations only declare readOnlyHint=true. The description adds substantial behavior beyond that: route filter dual-matching semantics, congestion interpretation (current > average), pagination via offset/limit, and the 24,000-byte response budget. No contradiction with annotations.

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?

Every sentence earns its place: purpose, usage, route filter semantics, congestion rule, and paging. The purpose is front-loaded and there is no padding or 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 and readOnlyHint annotation, the description covers all needed invocation details: what the tool returns, how to filter, paging behavior, and how to interpret congestion. Nothing critical 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?

Schema coverage is 100%, so baseline is 3. The description adds value by explaining the route parameter's two matching modes (designation vs. corridor-name substring) and how limit interacts with the byte-budget page cutoff, going beyond the schema's per-parameter docs.

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 states a specific verb and resource: 'Returns current vs. average travel times for named WA highway corridors' with concrete examples (I-5, SR 520). This clearly distinguishes it from ferry, border, toll, and pass tools in the sibling list.

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 says 'Use for "how congested is I-5?" or commute time estimates,' giving clear when-to-use context. It does not provide explicit exclusions or alternatives, but the sibling tools are in obviously different domains, so the guidance is adequate without them.

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 tools Inspect

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.