io.github.Unselfisheologism/supercarto
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| HERE_API_KEY | No | HERE API key; enables the get_traffic tool. | |
| TOMTOM_API_KEY | No | TomTom API key; enables the get_traffic tool. | |
| SUPERCARTO_GTFS | No | Path to a GTFS feed (directory or .zip); enables the get_transit and get_transit_route tools. | |
| OVERPASS_ENDPOINT | No | Your own Overpass instance endpoint. | |
| SUPERCARTO_GTFS_RT | No | GTFS-Realtime TripUpdates URL; adds live delay lines to get_transit. | |
| SUPERCARTO_PMTILES | No | PMTiles archive URL; primary data source when set (production use). | |
| TERRARIUM_ENDPOINT | No | Elevation tile template endpoint. | |
| SUPERCARTO_NO_TERRAIN | No | Disable elevation/terrain. | |
| SUPERCARTO_NO_WEATHER | No | Disable weather. |
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
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_mapletA | Fetch real map data around a coordinate and return a token-budgeted topological graph: named places joined by walkable edges with distances in metres and compass directions. Use this to answer 'what is near X' and 'how do I get from A to B'. Omissions are reported, so treat a missing feature as not-shown rather than absent. |
| localizeA | Move within a map session you already hold. Pass the session SCR (from get_maplet with returnScr, or from the last localize) and your new position; the answer is only the delta: + places that entered view, - places that left it, ~ places that moved or updated. Store the updated SCR from the second content block and discard the old one. |
| routeB | Feasibility between two coordinates: straight-line distance, the compass direction to head, and nothing that pretends to be turn-by-turn navigation. Turn-by-turn comes only from a routing engine the operator has verified; the default answer ends in "verify the approach on arrival", which is the honest limit of what it computes. |
| search_placesA | Find named places (cafes, stations, shops) near a coordinate. Cheaper than get_maplet when only names are needed. |
| expand_featureA | Fetch the exact geometry of features by id, as WKT. Use only when shape matters, such as checking whether a route clears a building. |
| get_terrainB | Sample ground elevation around a coordinate, in metres. Returns the range plus high and low points, which is what an agent needs for grade reasoning. |
| get_weatherA | Current weather conditions and a short forecast at a coordinate. Use this before telling someone to walk, cycle, or drive, or to pick between an indoor and outdoor option. Reports what is actually falling (rain, snow, sleet) rather than only a temperature. |
| get_airA | Air quality at a coordinate: European and US AQI bands, particulate load, and the forecast window. Use this before sending someone into prolonged outdoor exertion, or before recommending a walking route to a person with respiratory sensitivities. |
| get_daylightA | Sun position, sunrise, sunset, and twilight state for a coordinate. Twilight is reported as day, civil, nautical, or night rather than a boolean, because "needs a torch" and "cannot see" are different states. |
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 9 tools
Each tool maps to a distinct data concern (terrain, air, daylight, weather, geometry, places, routing, session delta), and descriptions explicitly steer callers between near-duplicates like search_places vs get_maplet. The one soft overlap is route vs get_maplet, both of which claim to answer 'how do I get from A to B', though route's straight-line-only framing partially disambiguates them.
Seven of nine tools use a predictable get_/verb_noun pattern (get_terrain, get_air, get_daylight, get_weather, get_maplet, search_places, expand_feature). expand_feature, localize, and route break the prefix convention but remain clear single-verb names, so the deviation is minor rather than confusing.
Nine tools is well within the sweet spot, and each covers a genuinely different facet of geospatial context rather than duplicating another. Nothing feels padded or conspicuously absent from the surface.
The set covers environmental context (terrain, air, daylight, weather), place discovery, geometry expansion, session-based panning, and route feasibility — a solid lifecycle for location reasoning. The main gap is forward geocoding (resolving an address or place name to a coordinate), which agents would need before using most other tools.