Country Borders Grounding Data

Overview

Pass a two-letter ISO country code to retrieve all neighboring countries sharing a land boundary. Responses detail the nation's full name, geographic region, subregion, and whether it is landlocked. Paid plans add geographic center coordinates for the requested country.

Live Test Country Borders Grounding Data Source →

The tool

Once your client is connected to the VerveContext server, this appears in its tool list as CountryBordersGroundingData. It is read-only and open-world — it fetches and never mutates anything on your side — so most clients call it without asking you to confirm.

{
  "name": "CountryBordersGroundingData",
  "arguments": {
    "country": "CA"
  }
}

You do not name the tool yourself; the model picks it. Asking about CA in the terms this source covers is enough for it to reach for CountryBordersGroundingData on its own — naming it explicitly also works, and is the way to force the call.

Connecting

One server URL covers every source in the catalog, including this one. Authorization is OAuth: the client opens a browser once, and there is no key to paste into a config file.

{
  "mcpServers": {
    "vervecontext": {
      "url": "https://api.vervecontext.com/v1/mcp"
    }
  }
}

https://api.vervecontext.com/v1/mcp

Per-client setup — Claude, Cursor, VS Code, ChatGPT — is on the MCP setup page.

Arguments

These are the properties on the tool's inputSchema, so a well-behaved client validates them before the call is made. Premium arguments are accepted on every plan but only take effect on plans that include them.

What the model gets back

The result carries a structuredContent object matching the tool's declared outputSchema, so a client reads fields without parsing prose. status is "ok" and error is null on success; a null field means the value was not available for that input, not that the call failed.

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18

{
  "status": "ok",
  "error": null,
  "data": {
    "country": "Canada",
    "cca2": "CA",
    "landlocked": false,
    "region": "Americas",
    "subregion": "Northern America",
    "coordinates": {
      "lat": 60,
      "lng": -95
    },
    "borders": [
      "USA"
    ]
  }
}

Response fields

Paths are relative to data. Premium fields are absent rather than zeroed on plans that do not include them, so check for presence instead of comparing to 0.

Why ground on it

A model can produce something that looks like this answer from its training data, and be confidently out of date or simply wrong. This source returns the current value in a shape you can check, which is the difference between an answer you can cite and one you have to hedge.

Point an evaluation at cca2: it is the field most worth pinning a claim to, and it is either present and current or absent — never plausibly invented.

Failure modes

Errors come back as tool errors carrying a sentence the model can act on, not a bare status code. Error handling covers the full list.

A call costs 2 credits each time the tool actually runs; a model that reasons about the tool without calling it costs nothing.

Use cases

Cross-Border Route Planning

Freight dispatchers check adjacent nations along transport corridors to verify transit jurisdictions and identify landlocked destinations needing sea-port rerouting.

Regional Market Expansion

E-commerce platforms identify neighboring territories around existing warehouses to sequence regional delivery coverage country by country.

Geopolitical Strategy Games

Game developers build realistic adjacency maps between territories to enforce valid troop movements across shared national borders.

Compliance Risk Screening

When auditing vendor supply chains, trade compliance officers flag suppliers operating adjacent to sanctioned territories.

Other ways to use Country Borders Grounding Data

Set up Country Borders Grounding Data on VerveContext, or reach the same source a different way. Your VerveContext account and credits work on all of them — one key, one balance.

Related

More in Geography: