Skip to main content
Glama
vmware-skills

vmware-vks

by vmware-skills
OverviewSchemaSourceRelated ServersScoreDiscussionsAdmin
Python
Remote

get_supervisor_kubeconfig

Read-onlyIdempotent

Retrieve a Supervisor Kubernetes kubeconfig for a vSphere Namespace, optionally writing it to a file to keep the short-lived session token out of agent context.

Instructions

[READ] Get a kubeconfig for the Supervisor K8s API endpoint.

Returns {namespace, kubeconfig} as a YAML string, or {namespace, written_to} when output_path is given. Use this for Supervisor-level access; use get_tkc_kubeconfig instead to reach workloads inside a TKC cluster. Security: it carries a short-lived session token — prefer output_path so the credential never enters agent context. This is the higher-privileged of the two kubeconfigs, and until now it had no way to avoid being returned inline while its sibling's docstring recommended exactly that.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
targetNovCenter in config.yaml; omit for the default.
namespaceYesvSphere Namespace to set as the kubeconfig context.
output_pathNoFile to write, e.g. '~/.kube/supervisor.yaml'. Omit to return the kubeconfig inline. Creates parent directories and truncates the file.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.9.1
    • addedInput schema / properties / output_path
      Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "File to write, e.g. '~/.kube/supervisor.yaml'. Omit to return the kubeconfig inline. Creates parent directories and truncates the file.",
+  "title": "Output Path"
+}
  2. Changed3 schema fields changedv1.8.14
    • addedInput schema / additionalProperties
      Added value: +false
    • addedInput schema / properties / namespace / description
      Added value: +"vSphere Namespace to set as the kubeconfig context."
    • addedInput schema / properties / target / description
      Added value: +"vCenter in config.yaml; omit for the default."
  3. Addedv1.5.26
  4. Removedv1.5.23
  5. First observedv1.3.2

TDQS

A4.8/5.0
Behavior5/5

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

Annotations already declare readOnlyHint, idempotentHint, and non-destructive behavior; the description adds security-relevant behavioral context: the credential is a short-lived session token, it is higher-privileged, and using output_path keeps the credential out of agent context. These details go well beyond the structured annotations.

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 reasonably compact and front-loads the core purpose before return format and security guidance. The historical aside about the sibling's docstring is slightly extra but does not undermine clarity.

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

Completeness5/5

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

Despite having no output schema, the description explicitly states the return shape in both invocation modes. Combined with full schema coverage and safety annotations, an agent has everything needed to call this tool correctly and safely.

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?

Schema description coverage is 100%, so the schema documents namespace, target, and output_path. The description adds real semantic value by explaining the two return modes: inline kubeconfig vs. written file when output_path is given, and why output_path is preferred.

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 states a specific verb and resource: 'Get a kubeconfig for the Supervisor K8s API endpoint.' It clearly distinguishes this tool from get_tkc_kubeconfig, so an agent can select it correctly without opening schemas.

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

Usage Guidelines5/5

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

It gives explicit routing guidance: use this for Supervisor-level access and use get_tkc_kubeconfig instead for workloads inside a TKC cluster. It also advises preferring output_path for security, which covers an important usage decision.

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

Install Server

Other Tools