k8s-mcp-server

Overview Schema Source Related Servers Discussions Admin

set_default_cluster

Sets a named cluster as the default, making it the target for subsequent Kubernetes operations. Provide the cluster name to update the active configuration.

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": "set_default_cluster"
  }
}

Input Schema

Name	Required	Description	Default
`name`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Aug 5, 2026

TDQS

D1.7/5.0

Behavior1/5

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

With no annotations and no output schema, the description carries the full burden of explaining side effects. It fails to disclose what setting a default cluster means, whether it affects future operations, persists, or requires special permissions.

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

Conciseness2/5

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

The description is very short, but this is under-specification rather than effective conciseness. The Args/Returns sections are terse yet uninformative, adding little value.

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?

Even for a simple one-parameter tool, the description is incomplete. It does not explain the purpose of a 'default cluster', how the setting is used, or what a successful return looks like, leaving the agent with a tautological overview.

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?

The schema's 'name' parameter has 0% description coverage, and the description only adds '集群名称' (cluster name), which adds essentially no semantic value beyond the parameter name itself. The description does not compensate for the schema gap.

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

Purpose2/5

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

The description '设置默认集群' is a direct translation of the tool name 'set_default_cluster', restating it without adding any specificity. It does not distinguish this tool from siblings beyond what the name already implies.

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 such as import_cluster or list_clusters. There is no mention of prerequisites, context, or exclusions.

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