Distance Calculator Skill

OnlineCredit Usage:1 per callTool:DistanceCalculatorSkill

The tool

Let your agent measure the distance between two points. Call it as an MCP tool to get miles, kilometers, bearing and direction from coordinates.

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

Tool call

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

What that looks like in a conversation

You don't name the tool — the model picks it. Asking about 36.7783 in the terms this source covers is enough for it to reach for DistanceCalculatorSkill on its own.

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.

Client config

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

Endpoint

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

Per-client setup — Claude Desktop, 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.

Argument	Type	Example	Description
`lat1`Required	number	`36.7783`	The latitude of the first location
`lon1`Required	number	`-119.4179`	The longitude of the first location
`lat2`Required	number	`34.0522`	The latitude of the second location
`lon2`Required	number	`-118.2437`	The longitude of the second location

What the model gets back

The result carries a structuredContent object matching the tool's declared outputSchema, so a client can read fields without parsing prose. status is "ok" on success and error is null; a null field means the value wasn't 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"
  }
}

Fields

Fields marked Premium need a paid plan. On a plan without them the key is absent rather than wrong, so a model never reasons over a substituted value.

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 with a sentence the model can act on, not a bare status code.

Status	What it means
`400 / 422`	The arguments didn't validate. The message names the offending one.
`401`	The OAuth session is invalid or expired — reconnect the server.
`403`	Out of credits. Not a bad key — the month's allowance is spent.
`404`	This skill isn't part of VerveKit. Check the catalog.
`429`	Brief rate limit. Retrying after a moment succeeds.

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 →

Use it in 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 →

Frequently asked questions

Do I have to tell the agent to use DistanceCalculatorSkill?

No. The tool's name and description are in the model's context once the server is connected, so it selects the tool when the question calls for it. Naming it explicitly works too and is useful when you want to force the call.

Does connecting the server expose every tool at once?

Yes — one connection lists the whole VerveKit catalog. Clients with a tool budget can usually filter the list; the credit cost is per call, so an unused tool costs nothing.

What does a call cost?

1 credit each time the tool actually runs. A model that reasons about the tool without calling it costs nothing.

Is there a REST version of this?

Yes — the same source is available as a plain HTTPS endpoint on APIVerve, linked above. Same data, same credits, same account.

What's Next?

Continue your journey with these recommended resources

Browse all skills

The full catalog for this door

Connect a client

Claude, Cursor, VS Code and the rest

Plans & credits

What a call costs and how usage resets

Was this page helpful?