Colorado DWR MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| DWR_API_KEY | No | Your Colorado Division of Water Resources API key (optional for basic usage) |
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 |
|---|---|
| get_surface_water_stationsC | Search for surface water stations in Colorado |
| get_surface_water_ts_dayC | Get daily time series data for a surface water station |
| get_water_rights_net_amountC | Get net amounts for water rights |
| get_well_permitsC | Search for well permits |
| get_active_admin_callsC | Get active administrative calls |
| query_dwr_apiC | Generic tool to query any Colorado DWR REST API endpoint |
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 6 tools
Most tools have distinct purposes targeting different DWR resources like administrative calls, surface water stations, water rights, and well permits. However, 'get_surface_water_stations' and 'get_surface_water_ts_day' could potentially be confused as both relate to surface water stations, though their actions (search vs. get time series) differ. The 'query_dwr_api' tool is clearly distinct as a generic fallback.
All tools follow a consistent 'get_' or 'query_' verb prefix with snake_case naming, making them predictable and readable. The pattern is uniform across all six tools, with no deviations in style or convention.
With 6 tools, the count is reasonable for a DWR data server, covering key resources like water stations, rights, and permits. It's slightly lean but not inadequate, as the generic 'query_dwr_api' tool can extend functionality. A few more specialized tools might enhance coverage, but this is well-scoped.
The tools cover read operations for major DWR data types, but there are notable gaps in lifecycle coverage. For example, there are no tools for creating, updating, or deleting records, which might be expected in a full administrative system. The generic query tool helps mitigate this, but the surface is incomplete for CRUD workflows.