vmware-avi

diff_ako_config

Read-onlyIdempotent

Preview pending Helm value changes for AKO configuration before running an upgrade. Empty diff means no changes would occur.

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 upgrade_ako_config — 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 get_ako_version and pass it to both.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "diff_ako_config"
  }
}

Input Schema

Name	Required	Description	Default
`chart_version`	No	Pin the chart, e.g. "1.11.1". Empty = registry latest.

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Addedv2.4.0Oct 18, 2026

TDQS

A4.9/5.0

Behavior5/5

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

Adds substantial context beyond the annotations: empty output means no change, credential values are shown as `<redacted>` by the skill (not the real value), and the moving-latest caveat explains why two runs can differ with no local change. That last note nuances idempotentHint honestly rather than contradicting it.

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?

Front-loaded with the mode tag and core purpose, then layered caveats. Every sentence earns its place: redaction note, preview guarantee, and non-idempotence warning are all actionable.

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?

A read-only preview tool with an output schema, so return structure needn't be repeated; the description still explains the empty-diff semantics and the redaction behavior. Nothing an agent needs to call it correctly is missing.

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%, so baseline is 3; the description adds real meaning by explaining that empty chart_version resolves the registry's moving latest and recommending get_ako_version be read and passed to both callers. It goes beyond the schema's terse 'Empty = registry latest.'

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: pending Helm value changes not yet applied, with `[READ]` signaling the mode. It clearly distinguishes itself from upgrade_ako_config (this is the preview of it) and from get_ako_config (current config, not pending diff).

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?

Explicit when-to-use: 'Use this before upgrade_ako_config — it runs the same command.' It also names the exact alternative (get_ako_version) needed when chart_version is empty. Nothing is left to inference.

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