Skip to main content
Glama
EdgeworthHitbox

Colorado DWR MCP Server

get_well_permits

Search for Colorado well permits by name or receipt number to access water resource data from the DWR REST API.

Instructions

Search for well permits

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
wellNameNoName of the well
receiptNoReceipt number
pageSizeNoNumber of results to return

Implementation Reference

  • The switch case handler for the 'get_well_permits' tool, which extracts arguments and calls the shared handleApiCall method with the specific endpoint 'wellpermits/wellpermit'.
    case "get_well_permits": {
        const args = request.params.arguments as any;
        return await this.handleApiCall("wellpermits/wellpermit", args);
    }
  • Zod schema defining the input parameters for the get_well_permits tool: wellName, receipt, pageSize.
    z.object({
        wellName: z.string().optional().describe("Name of the well"),
        receipt: z.string().optional().describe("Receipt number"),
        pageSize: z.number().optional().describe("Number of results to return"),
    })
  • src/index.ts:95-105 (registration)
    Registration of the 'get_well_permits' tool in the ListTools response, including name, description, and inputSchema.
    {
        name: "get_well_permits",
        description: "Search for well permits",
        inputSchema: zodToJsonSchema(
            z.object({
                wellName: z.string().optional().describe("Name of the well"),
                receipt: z.string().optional().describe("Receipt number"),
                pageSize: z.number().optional().describe("Number of results to return"),
            })
        ),
    },
  • The handleApiCall method that performs the actual API request to the DWR REST API, formats parameters, adds apiKey if available, and returns the JSON response. This is the core logic executed by the get_well_permits handler.
    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?

No annotations are provided, so the description carries full burden for behavioral disclosure. It only states 'Search for well permits', which implies a read operation but lacks details on permissions, rate limits, pagination (despite a pageSize parameter), or response format. This is inadequate for a tool with parameters and no output schema.

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. It is appropriately sized and front-loaded, directly stating the tool's purpose. Every word earns its place, making it highly concise and well-structured.

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 tool has 3 parameters, no annotations, and no output schema, the description is incomplete. It fails to explain behavioral aspects like search behavior, result format, or usage context. For a search tool with multiple inputs, more detail is needed to guide effective use, especially without structured output information.

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?

Schema description coverage is 100%, so the schema already documents all three parameters (wellName, receipt, pageSize) with descriptions. The description adds no additional meaning beyond what the schema provides, such as how parameters interact or search logic. Baseline 3 is appropriate as the schema handles parameter documentation.

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 'Search for well permits' clearly states the verb (search) and resource (well permits), providing basic purpose. However, it lacks specificity about scope or differentiation from sibling tools like query_dwr_api, making it somewhat vague. It doesn't restate the name/title tautologically, but could be more detailed.

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?

The description provides no guidance on when to use this tool versus alternatives like query_dwr_api or other sibling tools. There is no mention of specific contexts, prerequisites, or exclusions. It merely states what the tool does without indicating appropriate usage 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