Skip to main content
Glama
lzinga

US Government Open Data MCP

bts_border_crossings

Read-only

Retrieve monthly statistics on trucks, personal vehicles, pedestrians, and rail crossings at U.S. ports of entry along the Mexican and Canadian borders, filterable by state, port, and measure type.

Instructions

Get border crossing data at U.S. ports of entry: trucks, personal vehicles, pedestrians, train passengers, containers. Covers U.S.-Mexico and U.S.-Canada borders. Monthly data by port, state, and measure type.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
stateNoState full name: 'Texas', 'California', 'New York'
borderNoBorder
port_nameNoPort of entry name: 'El Paso', 'San Ysidro', 'Detroit'
measureNoMeasure type: 'Trucks' (Commercial trucks), 'Personal Vehicles' (Personal vehicles (cars)), 'Pedestrians' (Foot traffic), 'Train Passengers' (Rail passengers), 'Rail Containers Loaded' (Rail freight containers (loaded)), 'Rail Containers Empty' (Rail freight containers (empty)), 'Buses' (Bus crossings)
limitNoMax results (default 20)
Behavior4/5

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

Annotations already declare readOnlyHint=true, so the tool is read-only. The description adds value by specifying the data is monthly and covers specific borders and measure types, which is not in annotations.

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 two sentences, front-loaded with the main action and scope. Every word adds value without redundancy.

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?

Despite no output schema, the description explains the returned data types, borders, and frequency. It adequately covers what the tool provides for a data retrieval function.

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 coverage is 100% with parameter descriptions. The tool description mentions 'monthly data' but adds little meaning beyond what the schema provides, so baseline score of 3 is appropriate.

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 clearly states the tool retrieves border crossing data at U.S. ports of entry, listing specific measure types and coverage of US-Mexico and US-Canada borders. This differentiates it from sibling tools which cover other topics.

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

Usage Guidelines2/5

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

No guidance is provided on when to use this tool versus alternatives. The description does not mention any prerequisites or exclusions.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/lzinga/us-gov-open-data-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server