Skip to main content
Glama

Borders

Search border crossings

search_border_crossings
Read-onlyIdempotent

Use this when the person names a border crossing, a town at a border, two countries or an airport and you need its id. Not for crossings around a place: use list_border_crossings_near. Answers border crossings and airports' passport control whose names, towns or countries match the words in any order, any language Borders knows, plurals, case or a typo: each with its id, its names, the two countries or the airport's city, and its link on borders.me; the closest names when nothing matches; at most 50.

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": {
      "query": "<query>"
    },
    "name": "search_border_crossings"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
queryYes

Output Schema

NameRequiredDescriptionDefault
crossingsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Beyond the annotations (which already declare read-only, idempotent, closed-world), the description discloses matching behavior: names, towns or countries in any order, any language, plurals, case and typo tolerance, plus a fallback of closest names when nothing matches and a result cap of 50. This is exactly the behavioral detail annotations cannot carry.

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 guidance is front-loaded before the matching semantics, and almost every clause adds information. The second sentence is long and dense, packing matching rules, fallback and result contents into one run-on, which slightly hurts scanability.

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 two-parameter lookup tool with annotations and an output schema, nothing essential is missing: trigger, exclusion, matching rules, fallback behavior and result cap are all stated. The enumeration of returned fields is mild redundancy given the output schema but not harmful.

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 0%, so the description has to compensate; it does so strongly for 'query' by explaining fuzzy, multi-token, multi-language matching that the bare string schema does not convey. The 'limit' parameter is only indirectly explained via 'at most 50', leaving the control of result count implicit.

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 (search border crossings) and immediately scopes it against a named sibling: 'Not for crossings around a place: use list_border_crossings_near.' An agent can distinguish intent 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?

Gives an explicit trigger ('the person names a border crossing, a town at a border, two countries or an airport and you need its id') and an explicit exclusion with the alternative tool to use instead. Both when and when-not are covered.

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