Skip to main content
Glama
vmware-skills

vmware-avi

by vmware-skills
OverviewSchemaSourceRelated ServersScoreDiscussionsAdmin
Python
Remote

ako_config_diff

Read-onlyIdempotent

Preview pending Helm value changes before applying an upgrade. Returns the Helm diff output; empty output means nothing would change, so use it to confirm what the upgrade will alter.

Instructions

[READ] Pending Helm value changes that have not been applied yet.

Returns helm's diff output; empty means nothing would change. Credential values in it read <redacted> — that is this skill blanking them, not the configured value. Use this before ako_config_upgrade — it runs the same command, so the preview is real. Note: with chart_version empty the registry's moving latest is resolved, so two runs can differ with no local change; read ako_version and pass it to both.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
chart_versionNoPin the chart, e.g. "1.11.1". Empty = registry latest.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv1.8.14
    • addedInput schema / additionalProperties
      Added value: +false
    • addedInput schema / properties / chart_version / description
      Added value: +"Pin the chart, e.g. \"1.11.1\". Empty = registry latest."
  2. Addedv1.8.8
  3. Removedv1.8.8
  4. Addedv1.5.29
  5. Removedv1.5.28
  6. First observedv1.5.22

TDQS

A4.9/5.0
Behavior5/5

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

The description adds behavior beyond annotations: redacted credentials, empty output semantics, and non-deterministic output when chart_version is empty due to moving latest. These are operational details an agent needs to interpret results correctly and do not contradict the read-only/idempotent effect annotations.

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 description is dense but every sentence carries necessary information: purpose, output semantics, redaction caveat, relationship to upgrade, and the version-pinning caveat. It is front-loaded with purpose and avoids filler.

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?

Given the one optional parameter, the read-only annotations, and the presence of an output schema, the description covers usage timing, output interpretation, credential masking, and the non-determinism caveat. Nothing essential is missing for selecting and invoking this tool.

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 coverage is 100% and the schema already documents chart_version, so the baseline is 3. The description adds value by explaining the practical effect of an empty value: the registry's moving latest is resolved and two runs can differ, plus the recommendation to pin using ako_version.

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 the marker '[READ]' and states a specific verb+resource: 'Pending Helm value changes that have not been applied yet,' then clarifies it returns 'helm's diff output.' This distinguishes it from read/show tools (ako_config_show) and aligns with the diff/upgrade family.

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 usage context: use before ako_config_upgrade, and says both run 'the same command,' so the preview is real. It also instructs the agent to read ako_version and pass it when chart_version is empty, providing a concrete safe invocation path.

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