Skip to main content
Glama
Sign In
k8s-mcp-server

k8s-mcp-server

by Tobewont
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

list_clusters

Retrieve a list of all imported Kubernetes clusters or view the configuration of a named cluster. Specify a cluster name to get its details.

Instructions

查看集群配置：不指定 name 时列出所有已导入集群，指定 name 时返回该集群详情

Args: name: 集群名称（可选）。省略则列出全部集群；指定则返回该集群的配置详情

Returns: 集群列表或单个集群配置

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

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

Input Schema

NameRequiredDescriptionDefault
nameNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4/5.0
Behavior3/5

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

With no annotations, the description carries the burden; it indicates a read-only 'view' operation and clarifies the list-vs-detail response based on the name parameter. It does not disclose potential permission requirements, error conditions, or response structure beyond what is stated.

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

Conciseness4/5

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

The description is brief and front-loaded, but it repeats the conditional behavior in the main description and again in the Args section (e.g., '指定则返回该集群的配置详情' vs '指定则返回该集群详情'). Minor redundancy prevents a 5.

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 tool with one optional parameter and no output schema, the description adequately covers behavior, parameters, and return type. It does not elaborate on pagination, authorization, or field details, but these are not expected for a basic list/detail operation.

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

Parameters5/5

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

Schema description coverage is 0%, but the description fully compensates by explaining the single name parameter: it is optional, omitting it lists all clusters, and specifying it returns cluster details. This adds critical meaning beyond the bare string/null schema.

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 uses a clear verb+resource ('查看集群配置') and specifies conditional behavior: omitting name lists all imported clusters, while specifying name returns cluster details. However, it does not explicitly differentiate from the sibling get_cluster_info, which may also return cluster details, so sibling distinction is incomplete.

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?

It gives clear context on when to omit or specify the name parameter, effectively describing the two usage modes. It does not name alternatives or state when not to use this tool, so it falls short of explicit exclusion guidance.

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

Deploy Server

Other Tools