Skip to main content
Glama
vmware-skills

vmware-avi

by vmware-skills
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

ako_sync_force

Destructive

Force a full AKO resync with the AVI Controller to rebuild Virtual Services and pools from current Kubernetes resources. Preview blast radius; on confirm, restart the AKO pod to fix drift.

Instructions

[WRITE] Force AKO to resync all K8s resources with the AVI Controller.

The resync restarts the AKO pod so it rebuilds every Virtual Service, pool and VS-VIP from the cluster's current resources. Without confirm=True this only previews: it returns blast_radius (context, namespace, the pod's name, uid and phase, and the Ingresses it re-programs) and changes nothing. Show that to the user and get their explicit decision. Do not set confirm=True on your own because the user asked earlier: they have not seen what it changes yet.

Refused with confirm=True: a pod already terminating, and a pod or Ingress list that cannot be read. Use when drift is detected; may cause brief traffic disruption. Run ako_sync_diff first to see what is out of sync, then ako_sync_status.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
confirmNoFalse (default) returns the blast radius and changes nothing. True applies it.
contextNoK8s context name (optional).
confirmedNoDeprecated alias for confirm; removed in the next minor release. confirmed=False holds even when confirm=True.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changedv1.10.0
    • addedInput schema / properties / confirm
      Added value: +{
+  "default": false,
+  "description": "False (default) returns the blast radius and changes nothing. True applies it.",
+  "title": "Confirm",
+  "type": "boolean"
+}
    • addedInput schema / properties / confirmed / anyOf
      Added value: +[
+  {
+    "type": "boolean"
+  },
+  {
+    "type": "null"
+  }
+]
    • changedInput schema / properties / confirmed / default
      Previous value: -falseNew value: +null
    • changedInput schema / properties / confirmed / description
      Previous value: -"false (the default) returns a preview and changes nothing; true forces the resync, which restarts the AKO pod so it rebuilds every Virtual Service, pool and VS-VIP from the cluster's current resources — brief traffic disruption is possible."New value: +"Deprecated alias for confirm; removed in the next minor release. confirmed=False holds even when confirm=True."
    • removedInput schema / properties / confirmed / type
      Removed value: -"boolean"
    • changedOutput schema / (root)
      Previous value: -{
-  "properties": {
-    "result": {
-      "title": "Result",
-      "type": "string"
-    }
-  },
-  "required": [
-    "result"
-  ],
-  "title": "ako_sync_forceOutput",
-  "type": "object"
-}New value: +null
  2. Changed3 schema fields changedv1.8.14
    • addedInput schema / additionalProperties
      Added value: +false
    • addedInput schema / properties / confirmed / description
      Added value: +"false (the default) returns a preview and changes nothing; true forces the resync, which restarts the AKO pod so it rebuilds every Virtual Service, pool and VS-VIP from the cluster's current resources — brief traffic disruption is possible."
    • addedInput schema / properties / context / description
      Added value: +"K8s context name (optional)."
  3. Addedv1.8.8
  4. Removedv1.8.8
  5. Addedv1.5.29
  6. Removedv1.5.28
  7. First observedv1.5.22

TDQS

A4.8/5.0
Behavior5/5

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

Annotations already flag destructiveHint=true, but the description goes well beyond that: it discloses that the resync restarts the pod, that without confirm=True it only previews and changes nothing, what the blast_radius contains, and the refusal conditions. No contradiction exists between description and 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 front-loaded with the action and label, then organized into preview behavior, safety guidance, refusal cases, and workflow. Every sentence contributes either a safety constraint, a usage condition, or an outcome description. It is detailed but not padded.

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?

The description is thorough for a destructive tool: it explains preview returns, refusal cases, traffic impact, and the recommended prior command. The only noticeable gap is that it does not state what a confirmed execution returns once applied, especially since no output schema exists. This is a minor omission given how much else is covered.

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 already 100% for all three parameters, so the baseline is 3. The description adds meaningful semantics for confirm: without it the tool is a no-op changing nothing, and it warns not to set confirm=True unilaterally. It also explains what a preview return looks like, which deepens the confirm parameter's meaning 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?

The description opens with a specific verb and resource: 'Force AKO to resync all K8s resources with the AVI Controller.' It then clarifies the mechanism (pod restart, rebuilding every Virtual Service, pool, and VS-VIP), making the tool's function unmistakable and distinct from read-only siblings like ako_sync_status and ako_sync_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?

The description gives explicit usage context: 'Use when drift is detected,' warns about traffic disruption, and prescribes a workflow: 'Run ako_sync_diff first... then ako_sync_status.' It also states a clear safety rule about not setting confirm=True without showing the user the preview, which is strong when-to-use guidance.

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