mcp-geoes
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
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_servicesC | List the services published by a source that has a catalog (ArcGIS). |
| describe_serviceB | Service metadata: layers with their ids, extent, CRS, formats, limits, and the capabilities this source actually supports. |
| describe_layerA | Describe a layer: fields with their types and coded-value domains, geometry type and record count. WMS sources publish no field schema and say so. |
| query_layerA | Query layer attributes and return GeoJSON in WGS84. Supports a SQL |
| identify_at_pointC | What is at a point: attributes at the given lon/lat (WGS84) for one or more layers of a source. |
| export_mapA | Render one source for a bbox [minlon,minlat,maxlon,maxlat] in WGS84 degrees and return it as an image. For several sources on one map use compose_map. |
| get_legendC | Legend of a source: structured entries (ArcGIS) or an image (WMS). |
| compose_mapA | Compose one map from several sources, aligned, with a combined legend. Name a |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| Catálogo de fuentes | Fuentes disponibles, sus capas clave y sus escalas nominales. |
| Matriz de capacidades | Qué puede responder cada fuente: la tabla de enrutado, explícita. |
TDQS
Scored across 8 tools
Each tool targets a distinct operation: listing services, describing services or layers, getting legends, querying attributes, identifying by point, and rendering maps. The overlap between query_layer and identify_at_point is minimal and well-differentiated by interaction style.
All tool names follow a clear verb_noun snake_case pattern (list_services, describe_layer, get_legend, export_map). Even identify_at_point fits the pattern with a prepositional phrase, and no mixed conventions appear.
Eight tools is well-scoped for a geospatial service client, covering discovery, metadata, query, legend retrieval, and map rendering without redundancy or bloat.
The tool surface covers the full geospatial workflow: catalog browsing, metadata inspection, query, point identification, legend access, single-source export, and multi-source composition. No obvious dead ends or missing core operations.