Skip to main content
Glama

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

Fastest border crossing

border_fastest_crossing
Read-onlyIdempotent

Rank border crossings by the current wait for a lane type and name the fastest. Pass crossings (e.g. ["San Ysidro", "Otay Mesa", "Tecate"]) or near (an area or state, e.g. "San Diego", "Juarez", "Niagara", "TX"). Drive time to each port is not included.

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_fastest_crossing"
  }
}

Input Schema

NameRequiredDescriptionDefault
laneNoLane type: car (general), sentri_nexus, ready_lane, pedestrian, pedestrian_ready, truck or truck_fast. Default car.
nearNoAn area or state instead of a list.
crossingsNoCrossing names to compare.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is covered. The description's genuinely additive note is the scope limitation that 'drive time to each port is not included,' which stops the agent over-interpreting results; however, it says nothing about data freshness guarantees, empty-match behavior, or what the ranking returns beyond the fastest name.

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?

Three short sentences, front-loaded with the action and its output, followed by the two parameter modes and a caveat. Every sentence carries distinct information and nothing is padded.

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?

There is no output schema, and the description only loosely conveys the return shape (a ranked ordering with the fastest named), which is a modest gap. Given the simple three-parameter surface and full annotation coverage, though, an agent has enough to call it correctly.

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 is 3, but the description goes further by supplying concrete example values for both 'crossings' ("San Ysidro", "Otay Mesa", "Tecate") and 'near' ("San Diego", "Juarez", "Niagara", "TX"), which materially helps an agent construct valid arguments that the schema alone does not.

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 verb and resource: 'Rank border crossings by the current wait for a lane type and name the fastest.' This clearly distinguishes the tool as a comparison/ranking operation rather than a raw listing, which differentiates it in spirit from siblings like border_wait_times_list, though no sibling is named explicitly.

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?

It explains the two input modes (pass a list of crossing names, or pass an area/state via 'near') which implies when each form is appropriate, but it never states when to prefer this tool over border_wait_times or border_wait_times_list, and gives no exclusions or failure conditions (e.g., unknown crossing name).

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.