Skip to main content
Glama
Mapbox MCP Server

Mapbox MCP Server

Official
by mapbox

Calculate Destination

destination_tool
Read-onlyIdempotent

Calculate a geographic point from an origin, bearing, and distance to find waypoints, search offsets, or locations north/east/south/west of a place using straight-line geodesic math offline.

Instructions

Calculate a destination point given a starting point, bearing, and distance using geodesic (great-circle) straight-line offset. Useful for "find a point 5km north of X", constructing search offsets, or computing waypoints. Bearing: 0=north, 90=east, 180/-180=south, -90=west. Note: this calculates a straight-line geographic offset, not road-network distance. Works offline without API calls.

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": {
      "origin": "<origin>",
      "distance": "<distance>",
      "bearing": "<bearing>"
    },
    "name": "destination_tool"
  }
}

Input Schema

NameRequiredDescriptionDefault
unitsNoUnits for the distancemeters
originYesStarting point
bearingYesDirection of travel in degrees (0=north, 90=east, -90=west, 180=south)
distanceYesDistance to travel

Output Schema

NameRequiredDescriptionDefault
unitsYesDistance units
bearingYesBearing used
distanceYesDistance traveled
destinationYesThe calculated destination point

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.18.1
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
    • changedOutput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
  2. First observedv0.12.6

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already cover safety and determinism (readOnly, idempotent, non-destructive, closed-world). The description adds meaningful context beyond them: the straight-line versus road-network caveat and the offline/no-API-call note. It needn't describe return values because an output schema exists.

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?

The purpose and method are front-loaded in the first clause, followed by use cases and caveats in a logical order. The bearing convention sentence duplicates the schema field description and could be dropped, but overall there is little wasted text.

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?

Given rich annotations, a 100%-covered schema, and an existing output schema, the description supplies exactly the missing pieces: the geodesic method, the use-case framing, and the straight-line limitation. An agent has everything needed to select and call it correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so all four parameters are already documented in structured data. The description's bearing convention (0=north, 90=east, 180/-180=south, -90=west) largely restates the schema's own bearing description and adds no new units or format guidance beyond it.

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?

Names a specific verb and resource ('Calculate a destination point') and pins down the exact inputs (starting point, bearing, distance) plus the method (geodesic great-circle offset). It also explicitly distinguishes itself from road-network tools, which separates it from directions_tool and isochrone_tool without needing their schemas.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives concrete use cases ('find a point 5km north of X', constructing search offsets, computing waypoints) and a clear negative condition ('not road-network distance'). It stops short of naming a specific sibling to use instead for road distances, so the routing is implied rather than explicit.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.