GeoAgent
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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 | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| geocodeA | Look up a place by name or airport code (e.g. "Bengaluru", "BLR") in the bundled dataset. Returns the place's name, kind, lat and lon, or an error if nothing matches. It returns coordinates only, never distances: to get a distance or bearing, call distance_bearing next. Always call this first for any place name instead of using remembered coordinates. |
| distance_bearingA | Geodesic distance in km and bearings in degrees from point 1 to point 2 (WGS84). Use this for every distance or bearing question. Never estimate a distance from memory. Get the coordinates from geocode first. |
| features_withinA | List all places within radius_km of a point, nearest first. kind can be "city" or "airport". Use for "what is within X km of ..." questions. Get the point from geocode first. |
| nearest_featuresA | The n nearest places to a point. kind can be "city" or "airport". Use for "closest" or "nearest" questions. Get the point from geocode first. |
| point_in_polygonA | True if the point is inside a GeoJSON Polygon or MultiPolygon (GeoJSON is lon, lat order). polygon_geojson is the GeoJSON object itself or a JSON string of it. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| geo_question | A system-style prompt that tells the model how to use the GeoAgent tools. |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| catalog | The dataset the tools search: every place with its kind and coordinates. |
TDQS
Scored across 5 tools
Each tool maps to a distinct geo operation, and the descriptions explicitly route agents (e.g. 'call distance_bearing next', 'get the point from geocode first'). The only mild overlap is features_within versus nearest_features, since a small radius query can approximate an n-nearest query, but the descriptions ('within X km' vs 'closest/nearest') resolve this adequately.
All names are snake_case and readable, but the grammatical conventions are mixed: geocode is a bare verb, distance_bearing and point_in_polygon are noun phrases, and features_within/nearest_features use noun+preposition forms. There is no single predictable verb_noun pattern to extrapolate from.
Five tools is a tight, well-scoped surface for a geo lookup/measurement agent, and each tool covers a genuinely different question type (geocode, measure, radius search, nearest-n, containment). Nothing feels redundant or missing from the count perspective.
The core lifecycle of place resolution, measurement, proximity search, and polygon containment is covered with no obvious dead ends in the stated workflow. The main gap is reverse geocoding (coordinates back to a place name), which agents would have to work around by scanning features_within results.