Disconnect from the currently connected virtual cluster. Optionally specify a kubeconfig path to close the active session.
Disconnect from the currently connected vcluster.
| Name | Required | Description | Default |
|---|---|---|---|
| kubeconfig_path | No |
Changes observed during successful MCP inspections.
v2.0.0Output schema / (root)Previous value: -{
- "$defs": {
- "CommandResult": {
- "properties": {
- "exit_code": {
- "title": "Exit Code",
- "type": "integer"
- },
- "output": {
- "title": "Output",
- "type": "string"
- }
- },
- "required": [
- "exit_code",
- "output"
- ],
- "title": "CommandResult",
- "type": "object"
- }
- },
- "properties": {
- "result": {
- "anyOf": [
- {
- "$ref": "#/$defs/CommandResult"
- },
- {
- "additionalProperties": {
- "type": "string"
- },
- "type": "object"
- },
- {
- "type": "string"
- }
- ],
- "title": "Result"
- }
- },
- "required": [
- "result"
- ],
- "title": "vcluster_disconnectOutput",
- "type": "object"
-}New value: +nullv0.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full behavioral burden. It discloses that the operation disconnects, but does not explain side effects, whether authentication is needed, what happens to the current kubeconfig context, or whether the optional kubeconfig_path affects which connection is terminated.
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, direct sentence with no filler or redundancy. The action is front-loaded and every word earns its place.
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?
For a tool with no annotations, no output schema, and one undocumented optional parameter, the description is too sparse. It gives enough to recognize the tool's purpose but not enough to invoke it correctly with confidence, especially regarding kubeconfig_path semantics and behavioral impact.
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 schema has one optional parameter, kubeconfig_path, with 0% schema description coverage, and the description does not mention it at all. An agent cannot determine whether the path identifies the connection, overrides the current context, or is irrelevant when null.
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 states a specific verb ('Disconnect') and a clear resource ('currently connected vcluster'). It is unambiguous and clearly distinguishable from sibling tools such as vcluster_list, vcluster_pause, or vcluster_delete.
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 implies the tool is used when a vcluster connection exists and should be terminated, but it does not explicitly state prerequisites, when to use this tool versus alternatives, or what 'currently connected' means in practice. Usage is implied rather than instructed.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.