Nutanix AIops

subnet_delete

Destructive

Delete a Nutanix subnet by extId. Use dry_run=true first to preview the irreversible removal and capture its prior state.

Instructions

[WRITE][risk=high] Delete a subnet. Destructive — pass dry_run=True to preview first.

Tagged risk=high (audit tier 'review'); NUTANIX_AUDIT_APPROVED_BY /
NUTANIX_AUDIT_RATIONALE optionally annotate who/why. Irreversible, so the
audit trail captures the subnet's full prior state (name, description, type,
VLAN id, cluster, IP config and pools).

Args:
    ext_id: Subnet extId as returned by subnet_list.
    dry_run: If True, return what WOULD be deleted without deleting.
    target: Prism Central target name from config; omit for the default.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "ext_id": "<ext_id>"
    },
    "name": "subnet_delete"
  }
}

Input Schema

Name	Required	Description	Default
`ext_id`	Yes
`target`	No
`dry_run`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Jul 28, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Annotations already declare destructiveHint=true and readOnlyHint=false, but the description goes well beyond them: it flags an audit tier ('review'), names the approval env vars (NUTANIX_AUDIT_APPROVED_BY/RATIONALE), explains irreversibility, and details what the audit trail captures (name, description, type, VLAN id, cluster, IP config and pools). This is rich behavioral context an agent needs before a high-risk mutation.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with [WRITE][risk=high] and the core action, then the preview hint, then audit metadata, then Args. The risk/audit section is slightly verbose but every sentence conveys operational meaning. Overall tight and well-ordered.

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?

For a high-risk destructive tool with no output schema and three zero-coverage params, the description covers the action, preview capability, audit/approval requirements, irreversibility, and all three parameters. It stops short of describing the return shape of dry_run output, but that is a minor gap for a delete tool.

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 description coverage is 0%, so the description must carry parameter meaning. It does: ext_id is explained as 'Subnet extId as returned by subnet_list', dry_run is described as a no-op preview, and target is identified as the Prism Central target name from config with a default-omit rule. This fully compensates for empty 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?

States a specific verb and resource ('Delete a subnet') and immediately adds the destructive nature and preview mechanism. Distinguishes itself from siblings like subnet_list/subnet_get/subnet_create by being the delete operation.

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?

Explicitly says to pass dry_run=True to preview before deleting, which is actionable when-to-use guidance. It does not name alternative tools or state when-not to use, but the preview-before-delete instruction is a clear usage directive.

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