Skip to main content
Glama

WritersLogic verifiable AI agents

geo-distance

Great-circle and WGS-84 ellipsoidal distance between coordinates — Computes the haversine (IUGG mean-radius sphere) and Vincenty inverse (WGS-84 ellipsoid) distance in metres plus initial and final bearings for up to 100 coordinate pairs, and optionally checks a claimed distance within a tolerance. Vincenty is millimetre-accurate except for nearly antipodal pairs, where it does not converge: those pairs return vincentyMeters null, status unknown and the haversine

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": {
      "pairs": "<pairs>"
    },
    "name": "geo-distance"
  }
}

Input Schema

NameRequiredDescriptionDefault
pairsYesCoordinate pairs.
claimBasisNoWhich distance claimedMeters is compared against (default vincenty).
toleranceMetersNoAllowed difference for claimedMeters (default 1).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior5/5

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

With no annotations, the description carries the full burden and does it well: it names the geodetic models (IUGG mean-radius sphere vs WGS-84 ellipsoid), states the accuracy claim (millimetre-accurate), and — most valuably — discloses the failure mode for nearly antipodal pairs, including the exact returned fields (vincentyMeters null, status unknown). That is behavior an agent could not infer from any structured field.

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?

One dense, front-loaded paragraph ordered from what it computes to model choice to edge case — the right priority. It is tightly packed and each clause carries information, though the final clause is truncated mid-thought ('and the haversine'), leaving the fallback behavior incomplete.

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?

No annotations and no output schema, so the description must cover both safety and return shape; it does cover the key output fields and the non-convergence case. What it omits is the full response structure (bearing fields, per-pair echo, status values on success) and the truncated haversine fallback description, which matters for a tool whose main complication is numeric edge cases.

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

Parameters4/5

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

Schema coverage is 100%, so baseline is 3, but the description earns a bump by explaining what the vincenty/haversine distinction actually means and why claimBasis matters, and by restating the 100-pair cap that bounds the pairs array. It still doesn't explain toleranceMeters semantics beyond the schema's own default note.

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?

States a specific verb and resource — computes haversine and Vincenty inverse distances between coordinate pairs, plus bearings — with scope (up to 100 pairs) and an optional verification mode. An agent immediately knows what the tool produces without opening the schema.

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 rather than stated: 'optionally checks a claimed distance within a tolerance' tells the agent that claim verification is a variant of this tool, but there is no explicit when-to-use or when-not-to-use guidance and no pointer to any alternative for coordinate work. Nothing is misleading, but routing is left to inference.

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