Skip to main content
Glama
IBM

chuk-mcp-geocoder

by IBM

distance_matrix

Calculate distances between multiple geographic points using the haversine formula. Accepts latitude/longitude coordinates or named location objects to generate a distance matrix in meters without external API calls.

Instructions

Compute haversine distance matrix between multiple points.

    Pure computation — no API calls needed. Accepts points as either
    [lat, lon] pairs or {"name": ..., "lat": ..., "lon": ...} objects.

    Args:
        points: JSON array of points. Each point is either:
                - [lat, lon] pair (auto-named "Point 1", "Point 2", ...)
                - {"name": "Label", "lat": 40.0, "lon": -105.0}
        output_mode: "json" (default) or "text"

    Returns:
        NxN distance matrix in metres between all point pairs
    

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pointsYes
output_modeNojson
Behavior4/5

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

With no annotations provided, the description carries full burden and does well by disclosing key behavioral traits: it's a pure computation tool (no API calls), specifies input formats, output modes, and the return structure (NxN matrix in metres). However, it doesn't mention performance characteristics or error handling.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is front-loaded with the core purpose, followed by structured sections for arguments and returns. Every sentence adds value with no redundancy, and the formatting enhances readability without unnecessary verbosity.

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?

For a computational tool with no annotations and no output schema, the description is largely complete: it covers purpose, behavior, parameters, and returns. The main gap is lack of explicit error cases or performance limits, but given the tool's simplicity, it's reasonably thorough.

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?

Given 0% schema description coverage, the description compensates effectively by explaining both parameters: 'points' with detailed format options and examples, and 'output_mode' with valid values. It adds meaningful context beyond the bare schema, though it could clarify JSON string formatting for the points parameter.

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 clearly states the specific action ('Compute haversine distance matrix') and resource ('between multiple points'), distinguishing it from sibling tools like geocode or route_waypoints. It precisely defines the mathematical operation and scope.

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?

The description implies usage through the mention of 'Pure computation — no API calls needed' and data format examples, but lacks explicit guidance on when to choose this tool over alternatives like route_waypoints or when not to use it. No prerequisites or comparisons are provided.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/IBM/chuk-mcp-geocoder'

If you have feedback or need assistance with the MCP directory API, please join our Discord server