Skip to main content
Glama

delete

Remove a specific Kubernetes resource like pods, deployments, or services from your cluster by specifying its type and name.

Instructions

Delete a Kubernetes resource

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
resourceYesThe resource type (pod, deployment, service, etc.)
nameYesThe name of the resource
namespaceNoThe namespace of the resource (optional, defaults to current context namespace)

Implementation Reference

  • The handler function for the 'delete' tool that executes the Kubernetes 'kubectl delete' command based on the provided resource type, name, and optional namespace.
    case "delete": {
      const { resource, name, namespace } = args;
      const nsArg = namespace ? `-n ${namespace}` : "";
      const cmd = `kubectl delete ${resource} ${name} ${nsArg}`;
      const { stdout } = await execAsync(cmd);
      return {
        content: [{ 
          type: "text", 
          text: stdout || `Deleted ${resource} ${name}` 
        }]
      };
    }
  • The input schema definition for the 'delete' tool, specifying parameters for resource type, name, and optional namespace.
    name: "delete",
    description: "Delete a Kubernetes resource",
    inputSchema: {
      type: "object",
      properties: {
        resource: { 
          type: "string",
          description: "The resource type (pod, deployment, service, etc.)"
        },
        name: { 
          type: "string",
          description: "The name of the resource"
        },
        namespace: { 
          type: "string",
          description: "The namespace of the resource (optional, defaults to current context namespace)"
        }
      },
      required: ["resource", "name"]
    }
  • server.js:1392-1394 (registration)
    The ListTools request handler that returns the list of all tools, including 'delete', for tool discovery.
    server.setRequestHandler(ListToolsRequestSchema, async () => {
      return { tools };
    });
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. 'Delete' implies a destructive mutation, but the description doesn't specify permissions required, whether the deletion is reversible, confirmation prompts, cascading effects, or error handling. This leaves significant gaps for a high-impact operation.

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 wasted words. It's appropriately sized and front-loaded, directly stating the tool's purpose without unnecessary elaboration.

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?

For a destructive mutation tool with no annotations and no output schema, the description is inadequate. It doesn't cover behavioral aspects like safety warnings, return values, or error conditions, which are critical given the tool's complexity and potential impact in a Kubernetes environment.

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%, with all parameters well-documented in the schema itself. The description adds no additional meaning beyond what's already in the schema (e.g., no examples of resource types, namespace defaults, or deletion strategies), so it meets the baseline for high schema coverage.

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 ('Delete') and target ('a Kubernetes resource'), providing a specific verb+resource combination. However, it doesn't differentiate this from other destructive operations like 'drain-node' or 'uncordon-node' among the many sibling tools, which would require a 5.

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 'delete' operations for specific resources (e.g., 'delete-pod' if it existed) or other destructive tools. It lacks any mention of prerequisites, exclusions, or comparative context with the extensive list of sibling tools.

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/thekaranpargaie/kube-mcp'

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