Establish a Kubernetes cluster connection by loading a kubeconfig context, or fall back to in-cluster config when no kubeconfig is available.
Load a kubeconfig context, or in-cluster config when no kubeconfig is available.
| Name | Required | Description | Default |
|---|---|---|---|
| context | No | ||
| namespace | No | default | |
| kubeconfig | No | ||
| session_name | No | default |
| Name | Required | Description | Default |
|---|---|---|---|
| result | Yes |
Changes observed during successful MCP inspections.
v1.0.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations provided, the description carries the full burden of disclosing behavioral traits. It does reveal the in-cluster fallback, but it omits significant side effects such as establishing a session via session_name, changing the active connection, or any persistence/replacement semantics. For a connection-management tool, this is insufficient transparency.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single, front-loaded sentence with no redundancy or filler. It earns its place as a concise summary, though it is too brief to cover the tool's full behavior and parameter semantics.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Despite having an output schema, the tool has 4 parameters with 0% schema description coverage and no annotations. The description is too minimal to let an agent confidently invoke the tool correctly; it does not explain the meaning of context, namespace, session_name, or what 'connect' changes about the environment.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 0%, so the description must compensate by explaining the four parameters. It only mentions 'kubeconfig' generically and provides no meaning for context, namespace, or session_name. An agent cannot infer parameter formats, relationships, or defaults beyond the schema itself.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description uses a specific verb and resource: 'Load a kubeconfig context, or in-cluster config when no kubeconfig is available.' It clearly identifies the tool's role as establishing/loading a Kubernetes connection context, distinguishing it from siblings like k8s_disconnect, k8s_status, and the various listing/action tools.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description does not provide guidance on when to use this tool versus alternatives. It mentions a fallback to in-cluster config when no kubeconfig is available, but that is a behavioral condition rather than usage guidance. No mention of prerequisites, sequence with other k8s tools, or when not to use it.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.