ovf-data-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": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| discover_datasetsC | Find public water datasets by catalogue identifier; results are bounded. |
| describe_datasetC | Inspect one dataset or layer, including schema, CRS, limits, and provenance. |
| water_shortage_districtsA | List officially declared water-shortage (drought) grades per district. These are administrative declarations by the water directorates, not measurements. grade_code: 720 (none), 721, 722, or 723 (most severe). |
| list_measurement_typesA | List authoritative metric codes, units, valid ranges, and data-type codes. |
| find_stationsB | Find gauges by registry ID, name, watercourse, or municipality. network: "surface" (rivers and lakes), "wells" (shallow groundwater), "deep-wells" (confined/layer aquifer), or "precipitation". |
| nearest_stationsB | Find public gauges nearest a WGS84 latitude/longitude. network: "surface" (rivers and lakes), "wells" (shallow groundwater), "deep-wells" (confined/layer aquifer), or "precipitation". |
| get_observationsC | Get raw observations for an explicit interval of at most 7 days. include_quality: add upstream quality codes and labels per observation. |
| inspect_coverageC | Resolve a station and report documented temporal coverage before querying. |
| aggregate_observationsC | Aggregate observations server-side over daily, ten-day, monthly, or yearly buckets. |
| compare_soil_depthsC | Compare aligned soil-moisture or temperature series across sensor depths. |
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 10 tools
Each tool targets a distinct purpose: dataset discovery, schema inspection, aggregation, soil-depth comparison, drought declarations, measurement-type metadata, station lookup, proximity search, raw observations, and coverage inspection. The only mild overlap is find_stations vs nearest_stations, but the descriptions (registry/name search vs geographic proximity) make the distinction fairly clear.
The naming is inconsistent, mixing verb-based names (discover_datasets, describe_dataset, aggregate_observations, compare_soil_depths, list_measurement_types, find_stations, get_observations, inspect_coverage) with noun-phrase names (water_shortage_districts, nearest_stations). Some use verb_noun (find_stations, describe_dataset), others drop the leading verb (nearest_stations, water_shortage_districts). The 'describe_dataset' vs 'discover_datasets' singular/plural mismatch also adds inconsistency.
Ten tools is a well-scoped surface for an observational water data domain, covering discovery, metadata, querying, and analysis. Each tool serves a distinct function and none feels like filler; the count is squarely in the ideal 3-15 range.
The surface covers discovery, metadata inspection, raw observation retrieval, aggregation, soil-depth comparison, station lookup, proximity search, and drought declarations. Minor gaps include no direct update/delete (not applicable to a read-oriented data service) and possibly no explicit download/export tool, but the core observational querying workflow appears complete.