vmware-nsx

Overview Schema Source Related Servers Score Discussions Admin

delete_static_route

Destructive

Delete a static route from a Tier-0 or Tier-1 gateway permanently. Traffic to that destination CIDR immediately falls back to remaining routes or is dropped; confirm route details first.

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. Run list_static_routes on the same tier1_id first to confirm the route_id, destination and next hops, and confirm with the user before deleting. gateway_type must match where the route lives. Returns a confirmation string, or an "Error: ..." string — not a dict.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`target`	No	NSX Manager target from config (default if omitted).
`route_id`	Yes	Static route ID to delete, as returned by list_static_routes.
`tier1_id`	Yes	Gateway that owns the route (Tier-0 or Tier-1, per gateway_type), from list_tier0_gateways / list_tier1_gateways.
`gateway_type`	No	Either "tier0" or "tier1" (default "tier1").	tier1

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed6 schema fields changedv1.8.16Sep 1, 2026

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."

Addedv1.8.9Aug 1, 2026
Removedv1.7.6Jul 22, 2026

Changed1 schema field changedv1.6.0Jun 22, 2026

addedInput schema / properties / gateway_type

Added value: +{
+  "default": "tier1",
+  "title": "Gateway Type",
+  "type": "string"
+}

First observedv1.3.2Mar 27, 2026

TDQS

A4.7/5.0

Behavior5/5

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

Beyond the annotations (destructiveHint=true, readOnlyHint=false), the description adds meaningful behavioral context: the operation is irreversible, traffic immediately falls back or gets dropped, one must confirm with the user, and the return value is a confirmation string or an 'Error: ...' string rather than a dict. This materially improves agent calibration.

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 compact and front-loaded with the operation type, followed by necessary warnings, preconditions, and return behavior. Every sentence contributes: irreversibility, traffic impact, prerequisite list, user confirmation, type constraint, and response format. No 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 4-parameter tool with annotations and full schema coverage, the description is complete. It covers prerequisites, destructive side effects, parameter consistency, user confirmation, and return shape. An agent has everything needed to safely invoke this tool and interpret the result.

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 the baseline is 3. The description adds value by tying route_id to list_static_routes output, clarifying that tier1_id must be the owning gateway according to gateway_type, and emphasizing that gateway_type must match where the route lives. This goes beyond the raw schema descriptions.

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 — 'Permanently delete a static route from a Tier-0 or Tier-1 gateway' — which precisely identifies the operation and distinguishes it from sibling tools like delete_tier1_gateway, delete_nat_rule, and create_static_route. No ambiguity about what is acted on.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The tool tells the agent to first run list_static_routes on the same tier1_id to confirm the route_id, destination, and next hops, and instructs user confirmation before deleting. It also requires gateway_type to match where the route lives. It does not explicitly name alternatives or when-not-to-use scenarios, but for a destructive route deletion the workflow guidance is clear enough.

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