Skip to main content
Glama
EdgeworthHitbox

Colorado DWR MCP Server

get_surface_water_stations

Search for surface water monitoring stations in Colorado using filters like station name, water division, county, or water district to access hydrological data.

Instructions

Search for surface water stations in Colorado

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
stationNameNoName of the station (supports wildcards like *AB*)
divisionNoWater division number (1-7)
countyNoCounty name
waterDistrictNoWater district number
pageSizeNoNumber of results to return (default 50)

Implementation Reference

  • Handler case for the get_surface_water_stations tool, dispatching to the generic API call handler with the specific endpoint 'surfacewater/surfacewaterstations'.
    case "get_surface_water_stations": {
        const args = request.params.arguments as any;
        return await this.handleApiCall("surfacewater/surfacewaterstations", args);
    }
  • Zod schema defining the input parameters for the get_surface_water_stations tool, converted to JSON schema for MCP.
    inputSchema: zodToJsonSchema(
        z.object({
            stationName: z.string().optional().describe("Name of the station (supports wildcards like *AB*)"),
            division: z.number().optional().describe("Water division number (1-7)"),
            county: z.string().optional().describe("County name"),
            waterDistrict: z.number().optional().describe("Water district number"),
            pageSize: z.number().optional().describe("Number of results to return (default 50)"),
        })
    ),
  • src/index.ts:60-72 (registration)
    Registration of the get_surface_water_stations tool in the list of tools returned by ListToolsRequestHandler.
    {
        name: "get_surface_water_stations",
        description: "Search for surface water stations in Colorado",
        inputSchema: zodToJsonSchema(
            z.object({
                stationName: z.string().optional().describe("Name of the station (supports wildcards like *AB*)"),
                division: z.number().optional().describe("Water division number (1-7)"),
                county: z.string().optional().describe("County name"),
                waterDistrict: z.number().optional().describe("Water district number"),
                pageSize: z.number().optional().describe("Number of results to return (default 50)"),
            })
        ),
    },
  • Generic helper method that executes the HTTP GET request to the Colorado DWR REST API, formats parameters, handles API key, and returns the JSON response as tool output. This is the core logic executed for get_surface_water_stations.
    public async handleApiCall(endpoint: string, params: any) {
        const url = `${BASE_URL}/${endpoint}`;
        const headers: Record<string, string> = {};
        if (this.apiKey) {
            headers["Authorization"] = this.apiKey; // Or however DWR expects it, docs say 'Token: ...' or query param
        }
    
        // DWR docs say: "Token: B9xxxxx-xxxx-4D47-y" in header OR apiKey query param
        // I'll use query param if apiKey is present to be safe/easy, or header if I can confirm.
        // Docs: "Request Header: ... Token: ..."
        // Let's stick to query params for simplicity if header format is custom.
        // Actually, let's use the params object.
    
        const finalParams = formatParams(params);
        if (this.apiKey) {
            finalParams["apiKey"] = this.apiKey;
        }
    
        console.error(`Fetching ${url} with params ${JSON.stringify(finalParams)}`);
    
        const response = await axios.get(url, {
            params: finalParams,
            headers,
        });
    
        return {
            content: [
                {
                    type: "text",
                    text: JSON.stringify(response.data, null, 2),
                },
            ],
        };
    }
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations provided, the description carries the full burden of behavioral disclosure. It states it's a search operation, implying read-only behavior, but doesn't mention any constraints like rate limits, authentication needs, or what happens with no results. For a search tool with zero annotation coverage, this leaves significant gaps in understanding its behavior.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, efficient sentence with no wasted words, clearly front-loaded with the core purpose. It's appropriately sized for a search tool with well-documented parameters.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the complexity (5 parameters, no annotations, no output schema), the description is incomplete. It doesn't explain the return format, pagination behavior (implied by pageSize), or error handling. For a search tool with multiple filtering options, more context is needed to guide effective use.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The schema description coverage is 100%, so all parameters are documented in the schema. The description adds no additional meaning beyond the schema, such as explaining relationships between parameters (e.g., how division and waterDistrict interact) or search semantics. Baseline 3 is appropriate when the schema handles parameter documentation.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the action ('Search for') and resource ('surface water stations in Colorado'), providing a specific purpose. However, it doesn't differentiate from sibling tools like 'get_surface_water_ts_day' or 'query_dwr_api', which might also involve surface water data, so it doesn't fully distinguish from alternatives.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance is provided on when to use this tool versus alternatives such as 'get_surface_water_ts_day' (which likely retrieves time-series data) or 'query_dwr_api' (which might be a more general query tool). The description lacks any context on prerequisites, exclusions, or recommended scenarios.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/EdgeworthHitbox/dwr-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server