Skip to main content
Glama

Agent Data Tools: Full list (every tool as its own definition)

Distance between coordinates: km, miles, bearing and midpoint

geo_distance
Read-only

Great-circle distance between two latitude/longitude points (haversine on the mean earth radius) in kilometres, miles and nautical miles, plus the initial compass bearing and the midpoint. Accurate to about 0.5% against the ellipsoid. Use for delivery radius, travel and proximity checks, or sorting places by distance; for coordinates of a place name use geocode first. Example: lat1=59.3293, lon1=18.0686, lat2=51.5072, lon2=-0.1276. Price $0.01/call via x402 USDC or a card key (/credits), first 25 free; failed calls free. Reads or computes only and changes nothing; each call is charged, so repeats are not free.

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": "geo_distance"
  }
}

Input Schema

NameRequiredDescriptionDefault
lat1YesLatitude of the first point (-90 to 90)
lat2YesLatitude of the second point
lon1YesLongitude of the first point (-180 to 180)
lon2YesLongitude of the second point

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, but the description still adds accuracy bounds (~0.5% vs ellipsoid), a cost model ($0.01/call via x402 or card key, 25 free, failed calls free), and explains the otherwise surprising idempotentHint=false by noting each repeat call is charged. It does not cover behaviour on invalid or out-of-range coordinates, so it stops short of full coverage.

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?

Front-loaded with the core computation and its outputs, then use cases, then pricing; no sentence is filler. It is dense for one paragraph, and "Reads or computes only and changes nothing" mildly restates readOnlyHint, but the length is justified by the amount of genuinely new information.

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?

There is no output schema, and the description compensates by naming every returned quantity (three distance units, initial bearing, midpoint) as well as its accuracy. For a four-required-parameter computation tool this is essentially complete; only output shape (object vs. formatted string) and invalid-input behaviour are left unstated.

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; the description rises above that by giving a concrete example (lat1=59.3293, lon1=18.0686, lat2=51.5072, lon2=-0.1276) that fixes the ordering of point 1 versus point 2. It adds no semantics for antimeridian crossing or pole handling, which would have been useful given the haversine method.

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?

Opens with a specific verb and resource ("Great-circle distance between two latitude/longitude points") and enumerates the outputs (km, miles, nautical miles, initial bearing, midpoint) plus the algorithm (haversine on mean earth radius). It also separates itself from the geocoding step with "for coordinates of a place name use geocode first", so an agent can tell it apart from place-lookup siblings without opening a schema.

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

Usage Guidelines5/5

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

Explicitly names the use cases (delivery radius, travel and proximity checks, sorting places by distance) and the exclusion/handoff case (place-name coordinates -> geocode first). The worked coordinate example makes the calling convention unambiguous for a first invocation.

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.