MCP4GVA
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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| gva_layer_infoA | Get metadata information about the GVA GIS layer (fields, geometry type, spatial reference, extent) |
| gva_queryC | Query features from the GVA GIS layer with SQL-like WHERE clause and optional parameters |
| gva_countC | Count features matching a WHERE clause |
| gva_export_geojsonC | Export features to GeoJSON format |
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 4 tools
The tools have mostly distinct purposes: gva_count counts features, gva_export_geojson exports data, gva_layer_info provides metadata, and gva_query retrieves features. However, gva_count and gva_query both involve WHERE clauses and could be slightly confused for simple counting tasks, though their outputs differ (count vs. feature list).
All tool names follow a consistent 'gva_' prefix with descriptive snake_case suffixes (e.g., count, export_geojson, layer_info, query). This pattern is uniform and predictable across all four tools, making them easy to identify and understand.
With 4 tools, the count is reasonable for a GIS data server, covering core operations like querying, exporting, counting, and metadata retrieval. It might benefit from additional tools for updates or spatial analysis, but it's well-scoped for basic interactions.
The tools cover read operations (query, count, export, metadata) well for a GIS layer, but there are notable gaps: no create, update, or delete tools, which limits full CRUD lifecycle coverage. This could cause agent failures if modifications are needed, though it's sufficient for query and export workflows.