Skip to main content
Glama
fastmcp-me

chuk-mcp-geocoder

by fastmcp-me

route_waypoints

Resolves ordered place names to coordinates, computes distances between consecutive waypoints, and returns total route 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?

With no annotations, the description fully bears the burden of disclosure. It states the algorithm (haversine distances), return structure (resolved waypoints, leg distances, total distance, bounding box), and retry behavior. No contradictions.

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 well-structured with clear sections (Args, Returns, CRITICAL). It is concise—no unnecessary words—and front-loads the core purpose. Every sentence adds value.

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?

Despite no output schema, the description fully documents return values (resolved waypoints, leg distances, total distance, bounding box). It also provides critical retry guidance, making it complete for a tool with only 2 parameters and no nested objects.

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

Parameters5/5

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

Schema description coverage is 0%, but the description fully explains both parameters: 'waypoints' is a JSON array of place names with an example, and 'output_mode' defaults to 'json' with 'text' as alternative. This adds essential meaning beyond the bare 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?

The description clearly states it geocodes waypoints and computes route distances, with a specific verb ('Geocode') and resource ('waypoints in order'). It distinguishes itself from sibling tools like 'geocode' (single place) and 'distance_matrix' (likely driving distances) by focusing on sequential waypoint resolution and haversine distances.

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?

The description includes explicit CRITICAL retry guidance for when waypoints fail, instructing to simplify names and test with geocode. However, it does not explicitly compare with sibling tools like 'distance_matrix' for when to use straight-line vs driving distances.

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

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