Skip to main content
Glama

Borders

Find the best crossing

find_best_crossing
Read-onlyIdempotent

Use this when the person asks which border crossing to take from where they are or will be. into is the country they are going to. Not for one crossing's lanes: use get_border_wait. Answers the crossings into the country named, from a town or lat and lon, ranked by the drive to each (Apple Maps) plus its wait now, each with the drive, the wait and the total.

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": "find_best_crossing"
  }
}

Input Schema

NameRequiredDescriptionDefault
latNo
lonNo
fromNoa town: Rzeszów, San Diego
intoNothe country they are going to: Ukraine, Poland, Canada
laneNocars (the default), trucks, coaches, walking, NEXUS, SENTRI, Ready Lane, FAST

Output Schema

NameRequiredDescriptionDefault
fromYes
intoYes
crossingsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds genuinely useful behavior beyond that: the ranking is a sum of Apple Maps drive time and the wait now, and each result carries drive, wait and total. It does not mention result count limits, caching/rate limits, or coverage gaps for countries without wait data, which keeps it below a 5.

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?

The usage trigger and the exclusion are front-loaded, and the closing sentence efficiently explains ranking and return fields. The sentence fragment "into is the country they are going to" is redundant with the schema description and could be dropped without loss.

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?

An output schema exists and the description still usefully previews the returned fields, so return values are adequately covered. The main remaining gap is that no parameters are required, yet the description never says whether from or lat/lon must be supplied, which matters for a tool that ranks by drive distance.

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 60%, so the schema already documents from, into and lane. The description adds the either-or semantics between from and lat/lon ("from a town or lat and lon"), which the schema does not state, but it restates "into is the country they are going to" verbatim from the schema and never mentions the lane filter, leaving one documented parameter unaddressed.

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 states a specific verb+resource+scope: rank the crossings into a named country, starting from a town or lat/lon, by drive plus current wait. It also names the sibling it is not (get_border_wait) so the agent can separate recommendation from single-crossing lookup without opening either schema.

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

Usage Guidelines5/5

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

It gives both an explicit trigger ("when the person asks which border crossing to take from where they are or will be") and an explicit exclusion with a redirect ("Not for one crossing's lanes: use get_border_wait"). Nothing about selection between these two is left to inference.

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.

Resources