k8s-mcp-server

Overview Schema Source Related Servers Discussions Admin

delete_cluster

Delete a Kubernetes cluster by name. Removes the cluster configuration and associated resources, cleaning up the environment.

Instructions

删除集群配置

Args: name: 集群名称

Returns: 删除结果

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "name": "<name>"
    },
    "name": "delete_cluster"
  }
}

Input Schema

Name	Required	Description	Default
`name`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Aug 5, 2026

TDQS

C2.9/5.0

Behavior2/5

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

Annotations are absent, so the description carries full responsibility. It mentions 'delete' but does not disclose side effects, reversibility, permission requirements, or whether this affects the live cluster or just its configuration. The distinction between 'delete cluster' and 'delete cluster configuration' is ambiguous, and no safety hints are provided.

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 extremely concise and well-structured, with an action line, explicit Args and Returns sections. Every word serves a purpose, and the format is easy to parse. It is not verbose or redundant.

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?

Despite the tool's simplicity, the description lacks essential context for a destructive operation. There is no output schema, and the return value is only '删除结果' (deletion result) without details. It fails to clarify the scope of deletion, making it incomplete for an agent to safely invoke the tool.

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 coverage is 0%, but the description compensates minimally by stating that 'name' is the cluster name. This adds semantic meaning beyond the bare property name, but it does not provide format constraints, examples, or how to obtain the name. For a single required parameter, it is adequate but not rich.

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 states a specific action ('删除集群配置' = delete cluster configuration) with a clear verb and resource. It distinguishes from siblings by focusing on cluster deletion rather than listing, importing, or getting info, though it does not explicitly differentiate from delete_kubeconfig or batch_delete_resources.

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. There is no mention of prerequisites, whether to prefer this over delete_kubeconfig for specific cases, or any context for when deletion is appropriate. The usage is only implied by the verb 'delete'.

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