Skip to main content
Glama

Borders

Find the time to leave

find_time_to_leave
Read-onlyIdempotent

Use this when the person must be across a border by a time and asks when to get in line. through_by is a time in their words (16:00, 4 pm tomorrow). Not for the wait now: use get_border_wait. Answers the latest time to join the line to be through by the time given, at today's pace and the usual for those hours, with how sure it is; in the crossing's time zone.

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>",
      "through_by": "<through_by>"
    },
    "name": "find_time_to_leave"
  }
}

Input Schema

NameRequiredDescriptionDefault
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
through_byYesa time in the person's words: 16:00, 4 pm tomorrow, Saturday 9:00

Output Schema

NameRequiredDescriptionDefault
whyYes
join_byYes
crossingYes
through_byYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.7/5.0
Behavior4/5

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

Going beyond the readOnly/idempotent/non-destructive annotations, the description explains how the answer is derived ('today's pace and the usual for those hours'), that a confidence measure accompanies it, and that the time is expressed in the crossing's time zone. It does not mention whether the result accounts for future conditions or what happens when no feasible join time exists, which keeps it from 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.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three dense sentences with no filler: trigger first, parameter clarification second, exclusion and alternative third, output shape last. Every sentence carries distinct information.

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 four-parameter, read-only estimation tool with a full schema and an output schema, nothing needed to call it correctly is missing — trigger, alternative, input interpretation, derivation basis, and time zone are all covered.

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 adds interpretation the schema does not: through_by is a time in the person's own words (16:00, 4 pm tomorrow) and the computation is anchored to the crossing's time zone. That resolves a real ambiguity about how a free-text time is interpreted.

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 names a specific outcome — the latest time to join the line to be through a border by a given time — using a concrete verb-and-resource pairing. It also explicitly distinguishes this from get_border_wait, so an agent can route between them 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 an explicit trigger ('when the person must be across a border by a time and asks when to get in line') and an explicit exclusion with the named alternative ('Not for the wait now: use get_border_wait'). Both when-to-use and when-not-to-use are stated.

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