Skip to main content
Glama
powerdrillai

Powerdrill MCP Server

Official
by powerdrillai

mcp_powerdrill_delete_dataset

Remove datasets from Powerdrill to manage storage and maintain organized AI data analysis environments.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
datasetIdYesThe ID of the dataset to delete

Implementation Reference

  • The main handler function for the mcp_powerdrill_delete_dataset tool. It extracts the datasetId from arguments, creates a PowerdrillClient instance, calls deleteDataset on it, and formats the success or error response as MCP content.
    async (args, extra) => {
      try {
        const { datasetId } = args;
    
        // Initialize Powerdrill client
        const client = new (await import('./utils/powerdrillClient.js')).PowerdrillClient();
    
        // Delete the dataset
        const response = await client.deleteDataset(datasetId);
    
        // Check if response is valid
        if (response.code !== 0) {
          throw new Error(`API returned error code: ${response.code}, message: ${response.message || 'No message'}`);
        }
    
        // Format the response as MCP content
        return {
          content: [
            {
              type: "text",
              text: JSON.stringify({
                success: true,
                message: `Dataset ${datasetId} successfully deleted`
              }, null, 2)
            }
          ]
        };
      } catch (error: any) {
        console.error(`Error deleting dataset: ${error.message}`);
        console.error(error.stack);
    
        // Return error response
        return {
          content: [
            {
              type: "text",
              text: JSON.stringify({
                error: `Error deleting dataset: ${error.message}`,
                errorType: error.name,
                errorStack: process.env.NODE_ENV === 'development' ? error.stack : undefined
              }, null, 2)
            }
          ],
          isError: true
        };
      }
    }
  • Input schema validation using Zod for the datasetId parameter.
    {
      datasetId: z.string().describe('The ID of the dataset to delete')
    },
  • src/index.ts:803-807 (registration)
    Registration of the tool with the MCP server using server.tool(), including name, schema, and handler reference.
    server.tool(
      'mcp_powerdrill_delete_dataset',
      {
        datasetId: z.string().describe('The ID of the dataset to delete')
      },
  • Supporting method in PowerdrillClient class that performs the actual HTTP DELETE request to the Powerdrill API endpoint `/datasets/{datasetId}`.
    async deleteDataset(datasetId: string) {
      try {
        const requestBody = {
          user_id: this.config.userId
        };
    
        const response = await this.client.delete(`/datasets/${datasetId}`, {
          data: requestBody
        });
        
        return response.data;
      } catch (error: any) {
        console.error(`Error deleting dataset ${datasetId}:`, error.message);
        throw error;
      }
    }
Behavior1/5

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

Tool has no description.

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

Conciseness1/5

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

Tool has no description.

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

Completeness1/5

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

Tool has no description.

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

Parameters1/5

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

Tool has no description.

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

Purpose1/5

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

Tool has no description.

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

Usage Guidelines1/5

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

Tool has no description.

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/powerdrillai/powerdrill-mcp'

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