Skip to main content
Glama

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.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • addedInput schema / properties / departingTerminalId / exclusiveMinimum
      Added value: +0
    • addedInput schema / properties / departingTerminalId / maximum
      Added value: +9007199254740991
    • changedInput schema / properties / departingTerminalId / type
      Previous value: -"number"New value: +"integer"
  2. Changed2 schema fields changed
    • removedOutput schema / properties / nextOffset / anyOf
      Removed value: -[
      -  {
      -    "type": "number"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • addedOutput schema / properties / nextOffset / 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": [
      +      "terminals",
      +      "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`: WSF Ferry API is unreachable or returns a non-2xx response after retries. `invalid_access_code`: WSF 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: -[
      -  "terminals",
      -  "totalCount",
      -  "nextOffset",
      -  "hasMore"
      -]
  4. Changed7 schema fields changed
    • addedInput schema / properties / limit
      Added value: +{
      +  "description": "Maximum terminals to return in this page (1–20). Defaults to 5. Counts terminals, not sailings.",
      +  "maximum": 20,
      +  "minimum": 1,
      +  "type": "integer"
      +}
    • addedInput schema / properties / offset
      Added value: +{
      +  "description": "Zero-based index of the first terminal to return, for paging. Defaults to 0.",
      +  "maximum": 9007199254740991,
      +  "minimum": 0,
      +  "type": "integer"
      +}
    • addedOutput schema / properties / hasMore
      Added value: +{
      +  "description": "True when more terminals 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 terminal space data is available or the filter matched nothing. Absent on normal results."New value: +"Informational 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."
    • changedOutput schema / properties / totalCount / description
      Previous value: -"Number of terminals returned."New value: +"Total terminals matching the filter across all pages (not just this page). Counts terminals, not sailings."
    • changedOutput schema / required
      Previous value: -[
      -  "terminals",
      -  "totalCount"
      -]New value: +[
      +  "terminals",
      +  "totalCount",
      +  "nextOffset",
      +  "hasMore"
      +]
  5. Changed7 schema fields changed
    • addedOutput schema / properties / terminals / items / properties / departingSpaces / items / properties / arrivingTerminalIds
      Added value: +{
      +  "description": "Numeric IDs of the terminals this sailing serves — the destinations. Pass one to wsdot_get_ferry_schedule as arrivingTerminalId, or resolve names with wsdot_get_ferry_terminals.",
      +  "items": {
      +    "type": "number"
      +  },
      +  "type": "array"
      +}
    • removedOutput schema / properties / terminals / items / properties / departingSpaces / items / properties / arrivingTerminalName
      Removed value: -{
      -  "description": "Destination terminal name.",
      -  "type": "string"
      -}
    • addedOutput schema / properties / terminals / items / properties / departingSpaces / items / properties / displayDriveUpSpace
      Added value: +{
      +  "description": "Whether WSF publishes a drive-up count for this sailing. False means driveUpSpaceCount is not reported, not that the lane is empty.",
      +  "type": "boolean"
      +}
    • addedOutput schema / properties / terminals / items / properties / departingSpaces / items / properties / displayReservableSpace
      Added value: +{
      +  "description": "Whether this sailing takes vehicle reservations. False means reservableSpaceCount does not apply.",
      +  "type": "boolean"
      +}
    • changedOutput schema / properties / terminals / items / properties / departingSpaces / items / properties / driveUpSpaceCount / description
      Previous value: -"Available drive-up vehicle spaces. Zero means full."New value: +"Available drive-up vehicle spaces. Zero means full — oversubscribed sailings report a negative count upstream and are floored to zero here, so this value is never negative."
    • addedOutput schema / properties / terminals / items / properties / departingSpaces / items / properties / itineraryLabel
      Added value: +{
      +  "description": "Upstream itinerary string for the sailing, e.g. \"Anacortes -> Friday Harbor\". A display label only — it may name the departing terminal or several stops, so do not read it as the destination.",
      +  "type": "string"
      +}
    • changedOutput schema / properties / terminals / items / properties / departingSpaces / items / properties / reservableSpaceCount / description
      Previous value: -"Available reservable vehicle spaces."New value: +"Available reservable vehicle spaces, floored at zero like driveUpSpaceCount. Zero means no reservable space remains."
  6. Changed2 schema fields changed
    • addedOutput schema / properties / notice
      Added value: +{
      +  "description": "Optional guidance when no terminal space data is available or the filter matched nothing. Absent on normal results.",
      +  "type": "string"
      +}
    • addedOutput schema / properties / terminalFilter
      Added value: +{
      +  "description": "The terminal ID filter applied, or absent if no filter was used.",
      +  "type": "number"
      +}
  7. First observed

TDQS

A4.8/5.0
Behavior5/5

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

The description adds substantial behavioral context beyond the readOnlyHint annotation: paging is by terminal, offset/limit select whole terminals, totalCount counts terminals not sailings, every sailing of a returned terminal is included, and driveUpSpaceCount of zero means the drive-up lane is full. It also clarifies that destinations are arrivingTerminalIds rather than itineraryLabel strings.

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?

The description is dense but every sentence earns its place. It front-loads the core purpose and use cases, then provides critical paging and field semantics. There is no filler or repetition of schema details.

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?

Given the output schema exists, the description does not need to explain return values in detail, yet it still highlights the key field driveUpSpaceCount and the paging behavior. It covers usage, terminal ID sourcing, destination ID semantics, and pagination, making it complete for an agent to invoke correctly.

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 meaning beyond the schema: it explains that limit/offset count terminals rather than sailings, that page size varies with the number of departures per terminal, and that departingTerminalId should be obtained from wsdot_get_ferry_terminals. This significantly helps an agent use the parameters correctly.

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 clearly scopes the tool's function and distinguishes it from related ferry tools by explaining that it answers 'will I make the ferry?' questions and that terminal IDs come from wsdot_get_ferry_terminals.

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 explicitly states when to use the tool: for 'will I make the ferry?' or 'how full is the next sailing?' questions. It also tells the agent to use wsdot_get_ferry_terminals to obtain a terminal ID. It does not explicitly state when not to use the tool versus ferry_schedule, but the use cases are clear enough.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.