Skip to main content
Glama
EdgeworthHitbox

Colorado DWR MCP Server

get_active_admin_calls

Retrieve active administrative calls for Colorado water divisions to monitor current water management restrictions and allocations.

Instructions

Get active administrative calls

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
divisionNoWater division number

Implementation Reference

  • Handler for the 'get_active_admin_calls' tool. Extracts arguments and delegates to the shared handleApiCall method with the specific endpoint 'administrativecalls/active'.
    case "get_active_admin_calls": {
        const args = request.params.arguments as any;
        return await this.handleApiCall("administrativecalls/active", args);
    }
  • src/index.ts:106-114 (registration)
    Registration of the 'get_active_admin_calls' tool in the list of available tools, including name, description, and input schema (optional division number).
    {
        name: "get_active_admin_calls",
        description: "Get active administrative calls",
        inputSchema: zodToJsonSchema(
            z.object({
                division: z.number().optional().describe("Water division number"),
            })
        ),
    },
  • Zod schema defining the input parameters for the tool: optional division number.
    z.object({
        division: z.number().optional().describe("Water division number"),
    })
  • Shared helper function that performs the actual API call to the DWR REST API endpoint, handles parameters, API key, and formats the response as MCP content.
    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),
                },
            ],
        };
    }
    
    async run(transport: any) {
Behavior2/5

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

With no annotations provided, the description carries full burden but only states the action without disclosing behavioral traits. It doesn't mention whether this is a read-only operation, potential rate limits, authentication needs, or what 'active' implies (e.g., real-time vs. cached data), leaving significant gaps in understanding how the tool behaves.

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 zero waste. It's appropriately sized and front-loaded, directly stating the tool's purpose without unnecessary elaboration, making it easy to parse quickly.

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 no annotations, no output schema, and a vague purpose, the description is incomplete. It doesn't clarify what 'administrative calls' are, what data is returned, or how the tool fits into the water management context implied by sibling tools, leaving the agent with insufficient information for 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 input schema has 100% description coverage, with the single parameter 'division' documented as 'Water division number'. The description adds no additional meaning beyond this, such as explaining what a water division is or how it affects results. Baseline 3 is appropriate since the schema does the heavy lifting.

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

Purpose3/5

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

The description 'Get active administrative calls' states the verb ('Get') and resource ('active administrative calls'), but it's vague about what 'administrative calls' are in this water management context. It doesn't distinguish from sibling tools like 'get_water_rights_net_amount' or 'get_well_permits', leaving ambiguity about the specific domain scope.

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. The description doesn't mention prerequisites, context (e.g., water division relevance), or exclusions, leaving the agent to infer usage from the tool name alone among unrelated siblings like 'get_surface_water_stations'.

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