kube_contextsList available kubectl contexts and mark the current one, so you can identify and select clusters without parsing raw CLI output.
List available kubectl contexts with current context marked.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
| Name | Required | Description | Default |
|---|---|---|---|
| current | Yes | ||
| contexts | Yes | ||
| retained | No |
Changes observed during successful MCP inspections.
v5.0.1Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The readOnlyHint annotation already communicates that this is a safe read operation. The description adds the useful behavioral detail that the current context is marked in the result, but does not discuss permissions, output format, or any other runtime behavior.
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?
A single, front-loaded sentence with no wasted words. It communicates the resource and the key distinguishing output detail immediately.
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?
Given the low complexity, zero parameters, and the presence of an output schema, the description is largely complete. An agent can understand what the tool returns, though it does not mention that the operation is read-only beyond the annotation.
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?
The tool has zero parameters, so there are no parameter semantics to document. The description does not need to compensate for any schema gaps, making the baseline score appropriate.
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?
States a specific verb and resource ('List available kubectl contexts') and adds that the current context is marked. It is clearly distinct in practice from siblings like kube_get, but it does not explicitly differentiate itself from alternatives.
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?
Usage is implied by the simple list operation: an agent would call this when it needs available kubectl contexts. However, the description gives no explicit when-to-use guidance or comparison to kubectl-related siblings such as kube_get.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.