Skip to main content
Glama

get_bounds

Convert a location name or coordinate geometry into a bounding box. Handles WKT, GeoJSON, and raw strings, outputting in various formats.

Instructions

Get converted coordinates for a bounding box or text location search. Supports parsing WKT, GeoJSON, ogrinfo extent, and raw coordinate strings. If MAPBOX_ACCESS_TOKEN is not set, you MUST provide explicit coordinates via 'bbox'.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
locationNoA text location to search for (e.g. 'New York City'). Requires MAPBOX_ACCESS_TOKEN env var. Either 'location' or 'bbox' MUST be provided.
bboxNoThe geometry to parse. Can be a raw bounding box string ('lat1,lng1,lat2,lng2'), a WKT polygon/linestring/point, a GeoJSON payload, or an `ogrinfo` extent block. The Minimum Bounding Rectangle (MBR) encapsulating the geometry will be extracted. Either 'location' or 'bbox' MUST be provided.
epsgNoThe projected EPSG code (e.g. '3857'). Defaults to '4326' (WGS84). Over 3,900 bundled projections; unknown codes are auto-fetched from epsg.io.
formatNoFormat of the output. Options: wkt, geojson-bbox, leaflet, overpass, ogc-bbox, kml, geojson-polygon, csv, stac-bbox. Default: csv.
coord_orderNoToggle between 'lng,lat' (default) and 'lat,lng' coordinate ordering in the formatted output. Useful for APIs that expect swapped coordinate orders.
zoomNoThe map zoom level (0-22) used to calculate the map tile coordinates for the centroid. Defaults to 15.
precisionNoThe number of decimal places to output coordinate strings as (defaults to 6).
Behavior3/5

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

No annotations provided, so description must cover behavioral aspects. It explains input formats, default EPSG, and that MBR is extracted. However, it does not explicitly state that the tool is read-only or non-destructive, nor does it mention any side effects or limitations beyond the environment variable dependency.

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?

Description is only three sentences, all dense with information: purpose, supported formats, and a critical usage condition. No redundant words. Front-loaded with the core action.

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?

Given the schema's 100% description coverage and absence of output schema, the description adequately covers the main use cases and constraints. It explains the two required parameter groups, format options, and EPSG handling. Minor gap: no mention of what happens if both 'location' and 'bbox' are provided (though schema enforces oneOf).

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?

Schema coverage is 100%, so baseline is 3. The description adds valuable context beyond schema: for 'location', it mentions the MAPBOX_ACCESS_TOKEN requirement; for 'bbox', it explains MBR extraction; for 'epsg', it notes over 3,900 bundled projections and auto-fetching. This enriches parameter understanding.

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 converted coordinates for a bounding box or text location search.' It specifies the core functionality (coordinate conversion) and distinguishes it from sibling tools that deal with Overpass, H3 indices, etc.

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?

Provides explicit guidance on when to use 'bbox' vs 'location': if MAPBOX_ACCESS_TOKEN is not set, must provide explicit coordinates via 'bbox'. This helps agents decide which parameter to use. However, it does not explicitly mention when not to use this tool or compare to alternatives.

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/iamvibhorsingh/bbox-mcp-server'

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