Skip to main content
Glama

wsdot-mcp-server

by io.github.cyanheads

Get Terminal Space

wsdot_get_terminal_space
Read-only

Returns real-time drive-up and reservable vehicle space available at WSF terminals for upcoming sailings. Use for "will I make the ferry?" or "how full is the next sailing?" questions. Optionally filter to a specific terminal by ID (use wsdot_get_ferry_terminals for the ID). driveUpSpaceCount is the key field — zero means the drive-up lane is full. Destinations are arrivingTerminalIds, not the itineraryLabel string: a sailing can serve several terminals, and those IDs are what wsdot_get_ferry_schedule accepts. Results are paged by terminal (default 5, max 20): offset/limit select whole terminals and totalCount counts matching terminals, not sailings — every sailing of a returned terminal is included, so page size varies with how many departures each terminal carries.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMaximum terminals to return in this page (1–20). Defaults to 5. Counts terminals, not sailings.
offsetNoZero-based index of the first terminal to return, for paging. Defaults to 0.
departingTerminalIdNoFilter to a specific terminal by numeric ID. Omit to return all terminals.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
errorNoPresent when the call failed. Absent on success.
noticeNoInformational note about the page window, or guidance when no terminal space data is available, the filter matched nothing, or the offset ran past the end.
hasMoreNoTrue when more terminals remain beyond the current page.
terminalsNoTerminal space availability by terminal.
nextOffsetNoOffset to pass to retrieve the next page, or null when this is the last page.
totalCountNoTotal terminals matching the filter across all pages (not just this page). Counts terminals, not sailings.
terminalFilterNoThe terminal ID filter applied, or absent if no filter was used.

TDQS

A5/5.0
Behavior5/5

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

Beyond the readOnlyHint annotation, the description discloses critical behavior: paging is by terminal (offset/limit select terminals, not sailings), totalCount counts terminals, every sailing for a returned terminal is included (so page size varies), and driveUpSpaceCount=0 means the lane is full. These nuances are not in the annotation and materially affect how the agent interprets results.

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 in the description adds value, from purpose to use cases to field semantics to paging behavior. It is front-loaded with the core purpose, then progressively deepens. No wasted words; the length is justified by the tool's complexity.

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?

Combined with the schema and annotations, the description covers all necessary aspects: what it returns, how to filter, how paging works, relation to sibling tools, and key output field interpretation. Given the output schema exists, return values need not be fully spelled out, and the description fills every practical gap an agent would face.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Although schema coverage is 100%, the description adds significant semantics: it explains that limit/offset operate on terminals rather than sailings, that departingTerminalId is optional and sourced from a specific sibling, and that the key output field (driveUpSpaceCount) has meaning. These go well beyond the parameter descriptions to ensure correct invocation and interpretation.

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 real-time drive-up and reservable vehicle space available at WSF terminals for upcoming sailings.' It immediately distinguishes itself with concrete use cases ('will I make the ferry?') and links to sibling tools (wsdot_get_ferry_terminals for IDs, wsdot_get_ferry_schedule for arriving terminal IDs), making the purpose unambiguous.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It explicitly states when to use the tool ('Use for "will I make the ferry?" or "how full is the next sailing?" questions'), advises how to obtain the terminal ID via a sibling tool, and clarifies the difference between arrivingTerminalIds and itineraryLabel to avoid misrouting to ferry_schedule. This is clear contextual routing with alternatives named.

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

A4.5/5.0
Disambiguation5/5

Every tool targets a distinct resource and action: border waits, ferry routes/schedules/alerts/terminals/space/vessel positions, mountain passes, toll rates, travel times, highway alerts, and cameras. No two tools overlap in purpose; even the two alert tools (ferry vs highway) are clearly separated by domain.

Naming Consistency5/5

All tools follow the wsdot_verb_noun pattern with snake_case. Most use 'get' (get_ferry_routes, get_border_waits, get_mountain_passes) and two use 'search' (search_alerts, search_cameras), which is appropriate for filtering operations. The single deviation (get_terminal_space instead of get_ferry_terminal_space) is minor and does not harm predictability.

Tool Count5/5

12 tools cover a broad but well-scoped domain of WSDOT transportation data. The ferry subsystem alone has 6 focused tools (routes, schedule, alerts, terminals, space, vessel locations), and other areas each have a dedicated tool. The count feels neither inflated nor sparse for the server's purpose.

Completeness5/5

The tool surface covers the full lifecycle of WSDOT information needs: real-time border waits, ferry operations (routes, schedule, alerts, terminal IDs, space, vessel tracking), road conditions (mountain passes, travel times, toll rates), safety alerts, and camera feeds. No obvious dead ends—every query type has a corresponding tool.

Resources