Skip to main content
Glama

FitzTopPicks APIs: calendars, recipes, names, places, sizes and more

Distance and bearing between two points

distance_between_points
Read-onlyIdempotent

How far apart are two places (in any coordinate format), and in which direction? Precise WGS84 distance in m, km, mi, nmi and ft, initial and final bearing and the midpoint. More APIs from FitzTopPicks: https://fitztoppicks.com/apis?utm_source=mcp-api&utm_medium=mcp&utm_campaign=more-apis

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": {
      "from": "<from>",
      "to": "<to>"
    },
    "name": "distance_between_points"
  }
}

Input Schema

NameRequiredDescriptionDefault
toYesEnd, any format.
refNoReference point for short plus codes (in the input, and to add a short code to the output), like "40.4,-79.9".
fromYesStart, any format.
orderNoFor letterless numbers: latlon (default) or lonlat. Hemisphere letters and lat/lon labels win.
methodNokarney (default) or vincenty.
inputFormatNoSkip auto-detection: latlon (dd/dms/ddm), utm, ups, mgrs, pluscode, geohash, maidenhead.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, non-open-world behavior, so the description needn't cover safety. It usefully adds behavioral content the annotations lack: that the computation is WGS84-based, that output includes distances in five units plus bearings and midpoint, and that a short plus code can be appended to output via ref. It omits any statement about auth, limits, or accuracy caveats for the two methods.

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 core is a tight two-sentence front-loaded statement of what is computed and returned. The trailing 'More APIs from FitzTopPicks' promotional URL is unrelated to tool selection and dilutes an otherwise efficient definition.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema, the description carries the return-value burden and does so adequately by listing units, bearings, and midpoint. Combined with 100% schema coverage on six parameters, an agent has enough to call it correctly; only the absence of method-accuracy trade-off notes leaves a minor gap.

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 the schema already explains from/to/ref/order/method/inputFormat, and the description largely restates them ('in any coordinate format', 'reference point'). Baseline 3 is appropriate since no new syntax or constraint detail beyond the schema is added.

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?

The description names a specific computation ('How far apart are two places... and in which direction') and enumerates the concrete results (WGS84 distance in m/km/mi/nmi/ft, initial and final bearing, midpoint). That output profile clearly separates it from coordinate-conversion or path-tracing siblings.

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

Usage Guidelines3/5

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

Usage is implied by the question framing — you use it when you want a distance and/or bearing between two locations. However, no explicit when-to-use/when-not-to-use guidance or named alternatives (e.g., convert_coordinates for pure format conversion, destination_point for projecting a point) are given, so the agent must infer routing.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources