geocoding-mcp
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": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| geocodeC | Forward geocode a location query using the Nominatim (OpenStreetMap) API. Returns latitude, longitude, and address details for matching places. |
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 1 tool
With only a single tool there is no possibility of overlap or misselection; 'geocode' has one unmistakable purpose (forward geocoding a query string).
The lone tool name 'geocode' is clear, lowercase, and well-chosen, but with just one tool there is no verb_noun pattern to demonstrate consistency across the set.
One tool is thin for a service whose domain (Nominatim) naturally includes forward and reverse geocoding plus lookup variants; the surface feels under-built rather than well-scoped.
Forward geocoding is covered, but obvious companion operations such as reverse geocoding (coordinates to address) and batch/multi-result lookup are absent, leaving notable gaps in the geocoding lifecycle.