Skip to main content
Glama

X420 agent services

x420_geo_distance

Read-onlyIdempotent

Distance and bearing: Great-circle distance (km, mi, nmi, m) and initial bearing between two coordinates. Pure computation. Not professional, legal, insurance, engineering, medical, financial or tax advice. Price: $0.01 USDC per call (x402 on Base). This hosted tool does NOT pay and does NOT return the deliverable: it validates the input and returns payment instructions (pay_to, network, price and the x402 URL to pay at). GET the url; read PAYMENT-REQUIRED from the 402; retry with PAYMENT-SIGNATURE (x402 v2). Or run the local x420-mcp server with your own wallet key to pay automatically. Deliverable once paid: JSON: km, mi, nmi, m, bearing_deg, compass.

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

Input Schema

NameRequiredDescriptionDefault
lat1Yesorigin latitude
lat2Yesdestination latitude
lon1Yesorigin longitude
lon2Yesdestination longitude

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive and open-world, and the description adds far more than required: price ($0.01 USDC on Base), the exact 402 challenge-and-retry handshake, and what a paid response contains. That is strong added context, but the definition is written as a pricing/flow primer and says nothing about precision, coordinate format expectations, or error behavior for invalid coordinates.

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?

Purpose is front-loaded in the first sentence and the critical caveat ('does NOT pay and does NOT return the deliverable') follows immediately. The middle section is dense and run-on, and the legal disclaimer plus restated deliverable fields push it past strictly necessary length.

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 compensates by enumerating the paid deliverable fields (km, mi, nmi, m, bearing_deg, compass) and fully documenting the x402 payment sequence. Missing coordinate-format and precision guidance is the main residual gap for a numeric-input tool.

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% with four required lat/lon parameters, so the schema already carries the semantics and a baseline 3 applies. The description mentions 'two coordinates' and the output fields but adds nothing the schema lacks, and notably never states that the parameters are strings requiring decimal-degree formatting.

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 computation: great-circle distance in four units plus initial bearing, between two coordinates, and labels it 'Pure computation.' An agent can distinguish it from geocode/reverse-geocode/elevation siblings 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 Guidelines4/5

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

Explicitly warns that this hosted variant does NOT perform the payment and does NOT return the deliverable, then gives the alternative path (run the local x420-mcp server with your own wallet key). It lacks explicit when-to-use-vs-sibling guidance (e.g., versus geocode), but the payment-flow guidance is unusually concrete.

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