k8s-mcp-server

Overview Schema Source Related Servers Discussions Admin

test_cluster_connection

Verify Kubernetes cluster connectivity by reloading kubeconfig from disk to use the latest credentials. Get connection test results for a specified cluster.

Instructions

测试集群连接（会从磁盘重新加载 kubeconfig，确保使用最新凭据）

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

Input Schema

Name	Required	Description	Default
`name`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Aug 5, 2026

TDQS

A4.2/5.0

Behavior3/5

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

With no annotations provided, the description carries the full burden. It discloses the significant behavior of reloading kubeconfig from disk, but does not mention side effects, authentication requirements, or what happens on failure. This is partial transparency.

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: a one-line purpose, an args section, and a returns section. Every sentence earns its place, and the structure is clear and front-loaded.

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

Completeness4/5

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

For a simple one-parameter test tool with no output schema, the description covers the essential purpose, behavior, argument, and return type. It does not elaborate on error cases, but given the simplicity and sibling context (e.g., check_cluster_health exists), it is reasonably complete and not under-specified.

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

Parameters4/5

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

Although the schema has no descriptions, the description explicitly lists 'name: 集群名称' (cluster name), providing meaning beyond the bare schema field. For a single parameter this is sufficient, but lacks deeper context like formats or defaults.

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

Purpose5/5

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

The description clearly states 'test cluster connection' with a specific verb and resource, and adds the unique behavior of reloading kubeconfig from disk. This distinguishes it from siblings like check_cluster_health or get_cluster_info.

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

Usage Guidelines4/5

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

The description implies usage is for testing connectivity with fresh credentials by reloading kubeconfig. It gives clear context but does not explicitly name alternatives or exclusion criteria, earning a 4 rather than 5.

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