Skip to main content
Glama
vmware-skills

vmware-vks

by vmware-skills
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

list_tkc_clusters

Read-onlyIdempotent

List TanzuKubernetesCluster (TKC) clusters across all namespaces or one namespace to view names, phases, and Kubernetes versions before fetching details or kubeconfig.

Instructions

[READ] List TanzuKubernetesCluster (TKC) clusters, optionally in one namespace.

Returns the family list envelope: {items: [{name, namespace, phase, k8s_version}], returned, limit, total, truncated, hint}. The Supervisor list is walked to completion, so truncated is always False. Start here, then call get_tkc_cluster for full detail or issue_tkc_kubeconfig for access. 'clusters' is a deprecated pre-1.8.0 alias of 'items', removed in 2.0 — read 'items'.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
targetNovCenter in config.yaml; omit for the default.
namespaceNovSphere Namespace to filter by. Omit to list every one.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv1.8.14
    • addedInput schema / additionalProperties
      Added value: +false
    • addedInput schema / properties / namespace / description
      Added value: +"vSphere Namespace to filter by. Omit to list every one."
    • addedInput schema / properties / target / description
      Added value: +"vCenter in config.yaml; omit for the default."
  2. Addedv1.8.9
  3. Removedv1.8.8
  4. Addedv1.5.26
  5. Removedv1.5.23
  6. First observedv1.3.2

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive, so the safety profile is covered. The description adds real behavioral context beyond that: the returned envelope shape, that the Supervisor list is walked to completion so 'truncated is always False', and the deprecation of the 'clusters' alias. It does not mention auth or rate-limit needs, so not a 5.

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?

Front-loads the [READ] tag and purpose, then envelope details, then the navigation hint. Well-ordered and largely tight, though the envelope field enumeration is somewhat dense for a description.

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

Completeness4/5

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

No output schema exists, so explaining the return envelope (items, returned, limit, total, truncated, hint) is valuable and done. Deprecation guidance is included. An agent has enough to call this correctly, though pagination/auth specifics are unstated.

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 both parameters (target, namespace) are already documented, making 3 the baseline. The description reinforces namespace scoping ('optionally in one namespace') but adds no syntax or format detail beyond the schema.

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?

States a specific verb+resource ('List TanzuKubernetesCluster (TKC) clusters') and adds the scope qualifier ('optionally in one namespace'). Clearly distinguishable from siblings like get_tkc_cluster (detail) and list_namespaces (different resource).

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?

Explicitly routes the agent: 'Start here, then call get_tkc_cluster for full detail or issue_tkc_kubeconfig for access.' This names both alternatives and the condition that selects each, leaving nothing to inference.

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

Deploy Server

Other Tools