Skip to main content
Glama

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

Border wait times at a crossing

border_wait_times
Read-onlyIdempotent

Current wait to enter the US at a land border crossing: passenger car general lanes, SENTRI or NEXUS, Ready Lane, pedestrian and commercial truck (FAST) lanes, lanes open, port hours, CBP notices and when CBP last reported. Accepts a port or bridge name (San Ysidro, Otay Mesa, Peace Arch, Ambassador Bridge, Rainbow Bridge), the city across the border (Tijuana, Juarez, Nuevo Laredo, Windsor, Vancouver), a state, or a CBP port number.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "crossing": "<crossing>"
    },
    "name": "border_wait_times"
  }
}

Input Schema

NameRequiredDescriptionDefault
crossingYesCrossing, city across the border, US border state, or CBP port number.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint and destructiveHint=false, so the description doesn't need to repeat safety. It does add genuinely useful behavior beyond them: the full field inventory (lane types, lanes open, port hours, CBP notices) and the freshness signal 'when CBP last reported', which tells the agent the data can be stale. It stops short of stating refresh cadence or handle behavior.

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 sentences, both front-loaded: the first states the outcome and the field coverage, the second states the accepted input forms. The enumeration is dense but each item corresponds to real returned data or a real identifier class, so nothing is filler.

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 output schema, the description carries the burden of describing return values and does so thoroughly, including the freshness timestamp. What remains unaddressed is disambiguation behavior — what happens with an ambiguous or unresolvable crossing name — and any guidance on choosing between this and the sibling tools.

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 the baseline would be 3, but the description adds concrete example values for each accepted identifier class (San Ysidro, Otay Mesa, Tijuana, Windsor, port number), which is more than the schema's generic gloss. That materially improves the agent's odds of constructing a resolvable 'crossing' value.

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 opens with a specific verb and resource — 'Current wait to enter the US at a land border crossing' — and enumerates the lane categories covered, so the agent knows exactly what data is returned. It does not, however, distinguish itself from the siblings border_wait_times_list or border_fastest_crossing, leaving the agent to infer that this is a single-crossing lookup.

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 only implicit: the required 'crossing' argument and the accepted identifier forms signal a single-crossing lookup, and the word 'Current' signals a live-data use case. There is no explicit when-to-use or when-not-to-use statement and no routing to the list or fastest-crossing siblings.

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.