Skip to main content
Glama
vmware-skills

vmware-vks

by vmware-skills
OverviewSchemaSourceRelated ServersScoreDiscussionsAdmin
Python
Remote

upgrade_tkc_cluster

Upgrade a Tanzu Kubernetes Cluster to a specified Kubernetes version. Use after listing available versions; the operation is asynchronous and cannot be reversed.

Instructions

[WRITE] Upgrade a TKC cluster to a new Kubernetes version.

Returns {name, namespace, new_version, status: "upgrading"}. Asynchronous and irreversible — Kubernetes cannot be downgraded, so poll get_tkc_cluster until phase is running. There is no dry run. Use this only for the K8s version; prefer scale_tkc_cluster for node counts.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesCluster name (via list_tkc_clusters).
targetNovCenter in config.yaml; omit for the default.
namespaceYesNamespace holding it.
k8s_versionYesTarget version from get_tkc_available_versions.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changedv1.8.14
    • addedInput schema / additionalProperties
      Added value: +false
    • addedInput schema / properties / k8s_version / description
      Added value: +"Target version from get_tkc_available_versions."
    • addedInput schema / properties / name / description
      Added value: +"Cluster name (via list_tkc_clusters)."
    • addedInput schema / properties / namespace / description
      Added value: +"Namespace holding it."
    • addedInput schema / properties / target / description
      Added value: +"vCenter in config.yaml; omit for the default."
  2. Addedv1.5.26
  3. Removedv1.5.23
  4. First observedv1.3.2

TDQS

A4.7/5.0
Behavior5/5

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

Beyond the annotations, the description discloses that the upgrade is asynchronous and irreversible, that downgrading is impossible, that no dry run exists, and it specifies the exact return shape. This is essential behavioral context for a mutating, non-idempotent tool, especially with no output schema.

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

Conciseness5/5

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

The definition is compact and front-loaded: purpose first, then return and behavior, then routing guidance. Every sentence earns its place, with no redundant or filler content.

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?

For a complex asynchronous mutation with no output schema, the description covers the critical operational details: what it returns, how to confirm completion, irreversibility, lack of dry run, and how to choose between this tool and scale_tkc_cluster. Nothing essential is missing.

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

Parameters3/5

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

Schema description coverage is 100%, so the input schema already documents all four parameters, including that k8s_version should come from get_tkc_available_versions. The description does not add parameter-level meaning beyond what the schema provides, so the baseline 3 applies.

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 opens with a specific verb and resource: 'Upgrade a TKC cluster to a new Kubernetes version.' It also clearly distinguishes this tool from scale_tkc_cluster by scoping it to Kubernetes version changes, making sibling differentiation easy.

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?

The description provides explicit usage guidance: 'Use this only for the K8s version; prefer scale_tkc_cluster for node counts.' It also instructs the agent to poll get_tkc_cluster until the phase is running and warns that there is no dry run.

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