Skip to main content
Glama

Borders

Get the usual wait

get_usual_wait
Read-onlyIdempotent

Use this when the person asks when to cross, which hour or day is quiet, or how long it usually takes. Not for the wait right now: use get_border_wait. Answers a crossing's usual wait by hour, Monday to Sunday, for one direction and lane (the car lane by default), from the past weeks' counts, with the shortest hours named and tonight's shortest; or one day's hours when day is given.

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

Input Schema

NameRequiredDescriptionDefault
dayNoa weekday: Saturday
laneNocars (the default), trucks, coaches, walking, NEXUS, SENTRI, Ready Lane, FAST
crossingYesa crossing's or airport's id as search_border_crossings shows it, or its name (Medyka, San Ysidro, Peace Bridge)
directionNothe country the lane goes into: Poland, Ukraine, the United States

Output Schema

NameRequiredDescriptionDefault
laneYes
weekYes
crossingYes
shortestYes
directionYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already cover read-only, idempotent, non-destructive and closed-world, so the bar is lower; the description still adds real context by disclosing the data provenance ('from the past weeks' counts') and the default lane. It does not state how fresh the counts are or how a missing/unknown crossing is handled, which keeps it off 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?

Usage and the sibling exclusion are front-loaded in the first two sentences, then the return shape follows. Slightly dense multi-clause sentences and a redundant restatement of the lane default (already in the schema) cost it a point, but there is no filler.

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

Completeness5/5

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

For a 4-parameter read tool with a full output schema and complete annotations, the description supplies the missing conceptual layer: what the aggregation is, what the default view is, and how `day` changes the result. Nothing an agent needs to select or call it correctly is absent.

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 baseline is 3, but the description adds the observable effect of `day` ('one day's hours when day is given') versus the default weekly-by-hour view, and clarifies `direction` as the country the lane goes into. That is meaning beyond the field-level descriptions rather than a restatement of them.

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?

States a specific verb and resource (returns a crossing's usual wait by hour, Monday to Sunday, for one direction and lane) and pins the scope against the current-wait sibling. The 'usual' vs 'right now' distinction makes it instantly separable from get_border_wait.

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?

Gives an explicit trigger ('when the person asks when to cross, which hour or day is quiet, or how long it usually takes') plus an explicit exclusion with the alternative named ('Not for the wait right now: use get_border_wait'). That is the when/when-not/alternative pattern in full.

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