Skip to main content
Glama
IBM

chuk-mcp-geocoder

by IBM

bbox_from_place

Generate bounding boxes for geographic locations to use with DEM/STAC geospatial tools. Input a place name to get coordinates in EPSG:4326 format for mapping and analysis workflows.

Instructions

Get a bounding box for a place, suitable for DEM/STAC tools.

    Returns bbox as [west, south, east, north] in EPSG:4326, compatible
    with dem_fetch, stac_search, dem_slope, and other geospatial tools.

    Args:
        query: Place name to get bbox for (e.g. "Palm Jumeirah, Dubai")
        padding: Fractional padding to expand bbox (0.1 = 10% on each side, default 0.0)
        output_mode: "json" (default) or "text"

    Returns:
        Bounding box [west, south, east, north], center point, and approximate area

    CRITICAL — LLM retry workflow when no results are found:
        If the query returns no results, you MUST retry automatically — do
        NOT ask the user. Simplify the query progressively:

        1. Remove specific landmarks/features, keep the broader place.
           "Strood Causeway, Mersea Island" → "Mersea Island"
        2. Drop region/country qualifiers if still no results.
           "Mersea Island, Essex, UK" → "Mersea Island"
        3. Try alternative or official names for the place.
        4. If using a broader place, consider adding padding to cover the
           area of interest (e.g. padding=0.1 for 10% expansion).

        Always retry at least twice before reporting failure.
    

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryYes
paddingNo
output_modeNojson
Behavior5/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It thoroughly describes the tool's behavior: the return format ('bbox as [west, south, east, north] in EPSG:4326'), output modes ('json' or 'text'), retry logic with specific steps, and error handling requirements ('retry automatically — do NOT ask the user'). This goes well beyond basic functionality.

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?

The description is well-structured with clear sections (purpose, returns, args, critical workflow) and uses bullet points for readability. While comprehensive, it might be slightly verbose; every sentence earns its place by providing essential information, but the retry section is detailed. It remains front-loaded with the core purpose first.

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 complexity (geospatial tool with retry logic), no annotations, and no output schema, the description is highly complete. It covers purpose, parameters, return values (including format and additional data like center point and area), usage context, and detailed error handling. This provides all necessary information for an AI agent to use the tool effectively.

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?

With 0% schema description coverage, the description fully compensates by explaining all three parameters: 'query' as a place name with examples, 'padding' as fractional expansion with a default, and 'output_mode' with options and default. It adds meaningful context beyond what the bare schema provides, such as the practical effect of padding values.

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: 'Get a bounding box for a place, suitable for DEM/STAC tools.' It specifies the verb ('Get'), resource ('bounding box for a place'), and distinguishes from siblings by focusing on bounding box retrieval rather than geocoding, routing, or other geospatial operations listed in the sibling tools.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides explicit usage guidance: it specifies when to use ('suitable for DEM/STAC tools' and lists compatible tools like dem_fetch, stac_search), includes a critical retry workflow with detailed steps for when no results are found, and implicitly distinguishes from siblings by not covering geocoding or routing functions. The retry instructions offer clear alternatives for handling failures.

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