Skip to main content
Glama
IBM

chuk-mcp-geocoder

by IBM

batch_geocode

Convert multiple place names to geographic coordinates in a single batch call, with per-query error handling and rate limit compliance.

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
queriesYes
limitNo
output_modeNojson
Behavior5/5

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

No annotations provided, so description carries full burden. It discloses sequential processing, rate limit respect, individual failures not aborting batch, and detailed retry guidance, making behavior fully transparent.

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?

Well-structured with sections (Args, Returns, retry guidance), but slightly verbose; each part earns its place, though could be more concise.

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?

Complete for a batch tool: explains all parameters, behavior, return format (coordinates or error per query), and retry guidance. No output schema needed given this detail.

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 description adds significant meaning: 'queries' is a JSON array with example, 'limit' is max results per query, 'output_mode' defaults to 'json' with 'text' option, all beyond what schema provides.

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 multiple place names in one call, distinguishing it from sibling tools like 'geocode' (single) and 'reverse_geocode'.

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?

It describes sequential processing to respect rate limits and gives retry guidance for failed queries, but does not explicitly state when to use this tool versus others.

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