Land-or-Sea Grounding Data

Overview

Coordinates are Sea works by analyzing the coordinates provided and checking if they are in the sea. It uses advanced algorithms to check if the coordinates are in the sea and returns if the coordinates are in the sea or not.

Live Test Land-or-Sea Grounding Data Source →

The tool

Once your client is connected to the VerveContext server, this appears in its tool list as Land-or-SeaGroundingData. 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": "Land-or-SeaGroundingData",
  "arguments": {
    "lat": "37.7749",
    "lon": "-122.4194"
  }
}

You do not name the tool yourself; the model picks it. Asking about 37.7749 in the terms this source covers is enough for it to reach for Land-or-SeaGroundingData 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

{
  "status": "ok",
  "error": null,
  "data": {
    "latitude": 37.7749,
    "longitude": -122.4194,
    "isSea": false
  }
}

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 latitude: 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

Maritime Fleet Tracking

When a vessel transmits GPS telemetry, fleet dispatchers verify if the craft is in open water before updating route status.

Delivery Address Verification

Flag erroneous delivery addresses or fake driver locations when reported coordinates point to water instead of land.

Marine Biology Research

Marine researchers filter animal tag pings to separate offshore migration waypoints from coastal land resting sites.

Emergency Dispatch Routing

To route distress beacons accurately, emergency responders check incoming coordinates to deploy coast guard vessels instead of ground crews.

Other ways to use Land-or-Sea Grounding Data

Set up Land-or-Sea 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: