Skip to main content
Glama

Caelara Labs Global Locale

distance_haversine_calc

Great-circle distance, initial bearing and midpoint between two coordinates

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": {
      "lat1": "<lat1>",
      "lon1": "<lon1>",
      "lat2": "<lat2>",
      "lon2": "<lon2>"
    },
    "name": "distance_haversine_calc"
  }
}

Input Schema

NameRequiredDescriptionDefault
lat1YesLatitude of point A
lat2YesLatitude of point B
lon1YesLongitude of point A
lon2YesLongitude of point B

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full burden. It does usefully disclose that three values are returned rather than just one, which is behavior beyond any structured field, but it omits critical traits such as output units (km vs miles), expected input units (degrees vs radians), and precision or edge-case handling.

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?

A single compact phrase with zero filler, and the outputs are packed in efficiently. The only weakness is that it is a bare fragment with no verb or leading context, though nothing is wasted.

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

Completeness3/5

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

For a four-parameter math tool with full schema coverage and no output schema, the description covers both inputs and outputs at a high level. It remains incomplete on units and earth-model assumptions, which materially affect how an agent interprets and presents results.

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 coordinate parameters are already documented as latitudes and longitudes of points A and B. The description adds no further meaning such as expected units or valid ranges, so the baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

Names the specific computation and its three outputs (distance, initial bearing, midpoint) for two coordinate pairs, which distinguishes it clearly from the other numeric/lookup siblings. It is a noun phrase with no verb, but the resource and result are unambiguous.

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

Usage Guidelines2/5

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

There is no statement of when to use this tool, no prerequisite or constraint, and no mention of assumptions such as spherical-earth model or coordinate order. The agent must infer the use case purely from the tool name.

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