Skip to main content
Glama
fastmcp-me

chuk-mcp-geocoder

by fastmcp-me

bbox_from_place

Retrieve bounding box coordinates for a place name, compatible with DEM and STAC geospatial tools. Returns west, south, east, north in EPSG:4326.

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
Behavior4/5

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

No annotations, so description carries full burden. Discloses return format (bbox, center, area) and EPSG:4326. Includes retry behavior. Does not cover rate limits or error handling beyond retry, but adequate for a read-only geocoding tool.

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?

First line front-loads core purpose. Retry workflow is detailed but necessary. Could be slightly more concise, but structure is logical and efficient for LLM guidance.

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

Completeness4/5

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

No output schema, but description explains return value. Covers all 3 parameters and includes retry logic. For a tool with 3 params and no nested objects, it is fairly complete.

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 coverage 0%, but description provides detailed semantics: 'query' with example, 'padding' as fractional expansion with default, 'output_mode' options. Adds meaning beyond 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?

Clear verb 'Get' and resource 'bounding box for a place'. Specifies bbox format as [west, south, east, north] in EPSG:4326 and lists compatible tools (dem_fetch, stac_search, etc.), distinguishing it from sibling geocoding tools.

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?

Explicitly states it is suitable for DEM/STAC tools and provides a detailed retry workflow on no results, guiding the LLM to simplify queries. Lacks explicit when-not-to-use, but the 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/fastmcp-me/chuk-mcp-geocoder'

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