quanta-route-geocoder
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| QUANTAROUTE_API_KEY | Yes | Your QuantaRoute API key. Get it from https://developers.quantaroute.com |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| geocodeC | Geocode an address to get DigiPin code and coordinates. Returns location information including latitude, longitude, and DigiPin. |
| reverse_geocodeB | Reverse geocode a DigiPin code to get coordinates and address information. |
| coordinates_to_digipinA | Convert latitude and longitude coordinates to a DigiPin code. |
| validate_digipinC | Validate a DigiPin format and check if it corresponds to a real location. |
| batch_geocodeA | Geocode multiple addresses in a single batch request (up to 100 addresses). |
| autocompleteA | Get autocomplete suggestions for addresses (minimum 3 characters). |
| lookup_location_from_coordinatesC | 🚀 REVOLUTIONARY: Get administrative boundaries (pincode, state, division, locality) from coordinates. Provides precision that even government services don't offer. |
| lookup_location_from_digipinB | 🚀 REVOLUTIONARY: Get administrative boundaries from a DigiPin code. |
| batch_location_lookupB | 🚀 REVOLUTIONARY: Batch lookup for multiple locations. Each location can be specified by coordinates or DigiPin (up to 100 locations). |
| find_nearby_boundariesA | Find nearby postal boundaries within a specified radius (NOT YET IMPLEMENTED - Coming Soon). The backend endpoint /v1/location/nearby needs to be implemented first. |
| get_usageA | Get API usage statistics and quota information. |
| get_location_statisticsA | Get live statistics about the Location Lookup service (total boundaries, states, divisions, etc.). |
| get_healthA | Check API health status and availability. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 13 tools
Most tools have distinct purposes: geocode handles addresses, reverse_geocode handles DigiPins, and lookup_location_* handles administrative boundaries. Some pairs share inputs (e.g., coordinates_to_digipin vs lookup_location_from_coordinates) and could be confused, but descriptions clarify the different outputs.
The naming mixes verb-first patterns (geocode, validate_digipin, get_usage) with noun-first phrases (coordinates_to_digipin, batch_location_lookup) and varied verbs (get, lookup, find). While readable, the lack of a uniform convention makes the set feel inconsistent.
13 tools is reasonable for a geocoding service covering geocoding, reverse geocoding, batch operations, autocomplete, validation, and administrative boundaries. The count is slightly inflated by the unimplemented find_nearby_boundaries tool and multiple meta endpoints, but overall well-scoped.
The core geocoding/reverse geocoding lifecycle is covered, including batch and autocomplete operations, plus administrative boundary lookups. Minor gaps include the missing nearby-boundaries functionality and no batch reverse geocoding from DigiPins to addresses, but these are workable or explicitly marked.