Skip to main content
Glama
chrishayuk

chuk-mcp-geocoder

by chrishayuk

route_waypoints

Geocode a list of place names in route order and compute haversine distances between consecutive waypoints, returning leg distances, total distance, and bounding box.

Instructions

Geocode waypoints in order and compute route distances.

    Resolves each waypoint to coordinates, then computes haversine
    distances between consecutive points.

    Args:
        waypoints: JSON array of place names in route order
                   (e.g. '["Boulder, CO", "Denver, CO", "Aspen, CO"]')
        output_mode: "json" (default) or "text"

    Returns:
        Resolved waypoints, leg distances, total distance, and bounding box

    CRITICAL — LLM retry guidance:
        If a waypoint fails to resolve, simplify its name and retry the
        entire route. Remove landmarks, qualifiers, and descriptive words.
        Use the single geocode tool to test problematic names first.
    

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
waypointsYes
output_modeNojson
Behavior5/5

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

Without annotations, description fully discloses behavior: resolves coordinates, computes haversine distances, returns specific fields (resolved waypoints, leg distances, total distance, bounding box), and retry strategy.

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?

Structured with Args, Returns, and critical guidance. Efficient with no fluff, though slightly long due to retry details.

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

Completeness5/5

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

For a 2-param tool with no output schema or annotations, description covers all aspects: parameters, behavior, return format, and error handling (retry). Complete and self-contained.

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 0%, but description explains waypoints as JSON array of place names with example and output_mode options and defaults. Adds meaning beyond schema.

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?

Description clearly states it geocodes waypoints in order and computes route distances. Distinguishes from siblings like geocode and batch_geocode by including routing behavior.

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?

Provides explicit retry guidance for waypoint resolution failures and references the single geocode tool for testing. Lacks explicit 'when not to use' but context is clear.

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/chrishayuk/chuk-mcp-geocoder'

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