Skip to main content
Glama
chrishayuk

chuk-mcp-geocoder

by chrishayuk

batch_geocode

Geocode multiple place names in a single batch request, returning coordinates or errors for each query while respecting Nominatim rate limits.

Instructions

Geocode multiple place names in one call.

    Each query is processed sequentially to respect Nominatim rate limits.
    Individual failures don't abort the batch.

    Args:
        queries: JSON array of place names (e.g. '["Boulder, CO", "Denver, CO"]')
        limit: Maximum results per query (default 1)
        output_mode: "json" (default) or "text"

    Returns:
        Per-query results with coordinates, or error for failed queries

    CRITICAL — LLM retry guidance:
        If any query in the batch fails, re-run only the failed queries
        with simplified names using the single geocode tool. Nominatim
        works best with simple place names — remove landmarks, qualifiers,
        and descriptive words before retrying.
    

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNo
queriesYes
output_modeNojson
Behavior5/5

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

Despite no annotations, the description fully discloses key behaviors: sequential processing to respect Nominatim rate limits, individual failures not aborting the batch, and specific LLM retry instructions. This provides sufficient transparency for safe invocation.

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) and concise language. Every sentence provides necessary information without redundancy, making it easy for an agent to parse quickly.

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?

Given the tool's complexity (batch processing with rate limits and error handling) and the absence of annotations or an output schema, the description is remarkably complete. It covers input format, behavior, error resilience, and even provides a failover strategy, leaving minimal ambiguity.

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?

With 0% schema description coverage, the description compensates by explaining the expected format for 'queries' (JSON array example), default values for 'limit' and 'output_mode', and valid values for 'output_mode'. Minor improvement would be clarifying that 'queries' is a JSON string, but it adds substantial meaning beyond the 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 the tool's purpose: 'Geocode multiple place names in one call.' This specific verb+resource combination immediately distinguishes it from sibling tools like 'geocode' (single) and 'reverse_geocode' (reverse).

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 implies usage for multiple place names and provides critical retry guidance for failures with a fallback to the single geocode tool. However, it does not explicitly state when not to use batch vs. alternatives or mention prerequisites, which would make it a 5.

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