Skip to main content
Glama
vmware-skills

vmware-nsx

by vmware-skills
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

delete_static_route

Destructive

Permanently delete a static route from a Tier-0 or Tier-1 gateway. Preview the blast radius first, then confirm to remove the route and reroute traffic.

Instructions

[WRITE] Permanently delete a static route from a Tier-0 or Tier-1 gateway.

Irreversible: traffic to the route's destination CIDR immediately falls back to remaining routes or is dropped. Without confirm=True this only previews: it returns blast_radius (the gateway, the route's network and next hops, blockers, unmeasured) and deletes nothing. Show that to the user and get their decision. Do not set confirm=True on your own because the user asked to delete earlier: they have not seen the blast radius yet. gateway_type must match where the route lives; a route_id not on that gateway is an error, and confirm=True refuses when the routes could not be read. Returns {"action": "preview" | "deleted", "blast_radius": ...}, else {"error", "hint", "blast_radius"?}.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
targetNoNSX Manager target from config (default if omitted).
confirmNoFalse (default) returns the blast radius and changes nothing. True applies it.
route_idYesStatic route ID to delete, as returned by list_static_routes.
tier1_idYesGateway that owns the route (Tier-0 or Tier-1, per gateway_type), from list_tier0_gateways / list_tier1_gateways.
gateway_typeNoEither "tier0" or "tier1" (default "tier1").tier1

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 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"
+}
    • changedOutput schema / (root)
      Previous value: -{
-  "properties": {
-    "result": {
-      "title": "Result",
-      "type": "string"
-    }
-  },
-  "required": [
-    "result"
-  ],
-  "title": "delete_static_routeOutput",
-  "type": "object"
-}New value: +null
  2. Changed6 schema fields changedv1.8.16
    • addedInput schema / additionalProperties
      Added value: +false
    • addedInput schema / properties / gateway_type / description
      Added value: +"Either \"tier0\" or \"tier1\" (default \"tier1\")."
    • addedInput schema / properties / gateway_type / enum
      Added value: +[
+  "tier0",
+  "tier1"
+]
    • addedInput schema / properties / route_id / description
      Added value: +"Static route ID to delete, as returned by list_static_routes."
    • addedInput schema / properties / target / description
      Added value: +"NSX Manager target from config (default if omitted)."
    • addedInput schema / properties / tier1_id / description
      Added value: +"Gateway that owns the route (Tier-0 or Tier-1, per gateway_type), from list_tier0_gateways / list_tier1_gateways."
  3. Addedv1.8.9
  4. Removedv1.7.6
  5. Changed1 schema field changedv1.6.0
    • addedInput schema / properties / gateway_type
      Added value: +{
+  "default": "tier1",
+  "title": "Gateway Type",
+  "type": "string"
+}
  6. First observedv1.3.2

TDQS

A5/5.0
Behavior5/5

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

The annotations already mark destructiveHint=true and readOnlyHint=false, but the description goes far beyond that by explaining irreversibility, immediate traffic fallback/drop, the preview-versus-apply behavior of confirm, refusal when routes cannot be read, and the return shape. This fully discloses the tool's behavioral profile.

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 earns its place. It front-loads the core action, immediately states irreversibility, then explains the preview workflow, user-decision requirement, error conditions, and return format. Nothing is redundant or 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?

For a destructive tool with five parameters and no output schema, the description is complete: it covers the operation, the required user-decision workflow, the blast radius contents, error behavior, and the exact return shape including the preview/deleted distinction. An agent has everything needed to invoke it safely.

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

Parameters5/5

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

Schema coverage is 100%, so the baseline is 3, but the description adds real meaning beyond the schema: confirm=True versus false is tied to preview/apply behavior, gateway_type must match where the route lives, and a route_id not on that gateway is an error. These are critical semantics not fully expressed in 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 states a specific verb and resource: 'Permanently delete a static route from a Tier-0 or Tier-1 gateway.' It clearly distinguishes this from sibling create/list tools and from deleting whole gateways. The scope is unambiguous.

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 when-to-use and when-not-to-use guidance: without confirm=True it previews the blast radius and deletes nothing; the agent must show the user the blast radius and get a decision; it must not set confirm=True on its own even if the user previously asked to delete. It also warns that gateway_type must match the route's gateway. This is exceptional usage 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