Distance Calculator Skill

Overview

Distance Calculator works by calculating the distance between two locations based on their latitude and longitude coordinates. It uses advanced algorithms to calculate the distance accurately and returns the distance in miles and kilometers.

Live Test Distance Calculator Skill Skill →

The tool

Once your client is connected to the VerveKit server, this appears in its tool list as DistanceCalculatorSkill. 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.

Tool call

{
  "name": "DistanceCalculatorSkill",
  "arguments": {
    "lat1": "36.7783",
    "lon1": "-119.4179",
    "lat2": "34.0522",
    "lon2": "-118.2437"
  }
}

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

Connecting

One server URL covers every skill 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": {
    "vervekit": {
      "url": "https://api.vervekit.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.

Argument	Type	Description
`lat1`Required	number	The latitude of the first location range -90–90
`lon1`Required	number	The longitude of the first location range -180–180
`lat2`Required	number	The latitude of the second location range -90–90
`lon2`Required	number	The longitude of the second location range -180–180

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.

Result

{
  "status": "ok",
  "error": null,
  "data": {
    "distanceMiles": 199.6804337234997,
    "distanceKm": 321.2535462758628,
    "location1": {
      "latitude": "36.728450",
      "longitude": "-119.53571",
      "city": "Sanger",
      "state": "California"
    },
    "location2": {
      "latitude": "34.044662",
      "longitude": "-118.24255",
      "city": "Los Angeles",
      "state": "California"
    },
    "bearing": 198,
    "direction": "South",
    "estimatedDriveTime": "5h 11m"
  }
}

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.

Field	Type	Example	Description
`distanceMiles`	number	`199.6804337234997`	Distance between the two locations in miles
`distanceKm`	number	`321.2535462758628`	Great-circle distance between the two points in kilometres
`location1`	object	`{…}`	Resolved origin location
`location1.latitude`	string	`36.728450`	Latitude of the origin in decimal degrees
`location1.longitude`	string	`-119.53571`	Longitude of the origin in decimal degrees
`location1.city`	string	`Sanger`	City the origin resolves to
`location1.state`	string	`California`	State or region the origin resolves to
`location2`	object	`{…}`	Resolved destination location
`location2.latitude`	string	`34.044662`	Latitude of the destination in decimal degrees
`location2.longitude`	string	`-118.24255`	Longitude of the destination in decimal degrees
`location2.city`	string	`Los Angeles`	City the destination resolves to
`location2.state`	string	`California`	State or region the destination resolves to
`bearing`Premium	number	`198`	Compass bearing in degrees (0-360) from location1 to location2
`direction`Premium	string	`South`	Cardinal direction: North, Northeast, East, Southeast, South, Southwest, West, Northwest
`estimatedDriveTime`Premium	string	`5h 11m`	Estimated driving time (e.g., 3h 45m)

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.

Status	What it means
`400` / `422`	The arguments did not validate. The message names the offending one.
`401`	The OAuth session is invalid or expired — reconnect the server.
`403`	Blocked by a key restriction or an IP allow-list. Never a bad identity.
`404`	This skill is not part of VerveKit. Check the catalog.
`429`	Out of credits, or a brief rate limit. The message tells them apart.

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

Delivery Radius Verification: Local couriers check mile distances between warehouse coordinates and customer dropoff points to confirm addresses fall within active delivery zones.
Road Trip Itinerary Planning: When travelers add stops to a route, travel apps calculate kilometer distances between waypoints to tally total travel distance.
Real Estate Search Filtering: Property portals measure distances from listed homes to city center coordinates so apartment hunters can filter rentals by commute proximity.
Fleet Dispatch Optimization: Dispatchers compute coordinate distances between open service tickets and available technicians to assign the nearest field worker to incoming jobs.

Other ways to use Distance Calculator Skill

Set up Distance Calculator Skill on VerveKit, or reach the same source a different way. Your VerveKit account and credits work on all of them — one key, one balance.

Call it as a REST APIOne HTTPS endpoint and an x-api-key header, with SDKs for Node, Python and .NET.APIVerve →Reference →

Google Sheets or ExcelA =VERVE() formula fills a column — no script, no export, recalculates in place.VerveSheets →Reference →

Ground an agent on itA cited, machine-checkable fact your model can't produce on its own.VerveContext →Reference →