Skip to main content
Glama

get_bounds

Convert bounding box coordinates or location text into standardized formats for geospatial applications. Parse WKT, GeoJSON, raw coordinates, or ogrinfo extents to extract bounding boxes in various output 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).
Behavior4/5

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

With no annotations provided, the description carries full burden and successfully discloses critical behavioral traits: MAPBOX_ACCESS_TOKEN dependency for geocoding, supported input formats (WKT, GeoJSON, ogrinfo), and the conversion nature of the tool. Could be improved by explicitly stating this is a safe read-only operation.

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?

Three sentences with zero waste: sentence 1 states purpose, sentence 2 lists parsing capabilities, sentence 3 provides the critical auth constraint. Front-loaded with the core action and appropriately sized for the tool's complexity.

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 7 parameters with 100% schema coverage and no output schema, the description appropriately focuses on high-level purpose and constraints rather than repeating schema details. Captures the essential context that this is a coordinate utility distinct from the server's data-retrieval siblings.

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%, establishing baseline 3. The description adds value by grouping the technical format details (WKT, GeoJSON, ogrinfo) into a cohesive capability statement for the 'bbox' parameter, and explicitly linking the MAPBOX_ACCESS_TOKEN requirement to the 'location' parameter behavior.

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 'Get[s] converted coordinates for a bounding box or text location search', providing specific verb and resource. It distinguishes from siblings (which focus on OSM data retrieval/H3 indices) by emphasizing coordinate conversion and parsing functionality.

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 conditional guidance: 'If MAPBOX_ACCESS_TOKEN is not set, you MUST provide explicit coordinates via 'bbox'.' This establishes clear prerequisites and when-to-use conditions for the location parameter. Does not explicitly reference sibling alternatives, but the coordinate conversion focus makes the distinction 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/iamvibhorsingh/bbox-mcp-server'

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