Skip to main content
Glama

Border Wait Times (US-Canada and US-Mexico) MCP

All border crossing wait times

border_wait_times_list
Read-onlyIdempotent

Wait times for one lane type at every CBP land port on the Mexican border, the Canadian border, or in one state (CA, AZ, NM, TX, WA, MT, ND, MN, MI, NY, VT, ME), sorted by the shortest wait or by name. Closed and pending lanes are listed after posted waits.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "border_wait_times_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
laneNoLane type: car (general), sentri_nexus, ready_lane, pedestrian, pedestrian_ready, truck or truck_fast. Default car.
sortNowait (default) or name.
stateNoUS border state, as a code or a name.
borderNomexico, canada or both (default both).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, so the safety profile is covered. The description goes beyond that by disclosing the sort behavior and, notably, that closed and pending lanes are appended after posted waits — a real ordering subtlety an agent would otherwise get wrong.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

One front-loaded sentence that opens with the resource and then layers scope, filters and sort order. Dense but free of filler; the parenthetical state list is the only slightly bulky element.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no required parameters, no output schema and strong annotations, the description supplies what the structured fields cannot: sort semantics and the treatment of closed lanes. Remaining gaps — whether state and border interact, and how many records come back — are modest for a read-only listing tool.

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

Parameters3/5

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

Schema description coverage is 100% and 3 of 4 parameters are enums, so the schema carries the semantics. The description adds little beyond it, except enumerating the twelve valid state codes, which the schema only describes generically as a code or name.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a specific resource (CBP land port wait times), the aggregation scope (every port on a chosen border or a single state), and the lane dimension. That breadth implicitly distinguishes it from the narrower sibling border_wait_times, but no sibling is named explicitly, so it falls short of a 5.

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

Usage Guidelines3/5

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

Usage is implied by the scope wording: this is the all-ports list, whereas border_fastest_crossing presumably answers 'which crossing is quickest'. There is no explicit when-to-use/when-not statement or named alternative, so the agent must infer the routing decision.

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.