Nutanix AIops

subnet_create

Destructive

Create a VLAN subnet on a Nutanix cluster by specifying its name, target cluster extId, and VLAN ID for network provisioning.

Instructions

[WRITE][risk=medium] Create a subnet on a cluster.

Args:
    name: New subnet name.
    cluster_ext_id: Target cluster extId (from cluster_list).
    vlan_id: VLAN / network id for the subnet.
    subnet_type: Subnet type (default VLAN).
    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": {
      "name": "<name>",
      "cluster_ext_id": "<cluster_ext_id>",
      "vlan_id": "<vlan_id>"
    },
    "name": "subnet_create"
  }
}

Input Schema

Name	Required	Default
`name`	Yes
`target`	No
`vlan_id`	Yes
`subnet_type`	No	VLAN
`cluster_ext_id`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Jul 28, 2026

TDQS

A3.6/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=false, idempotentHint=false, and destructiveHint=true, so the safety profile is covered. The description adds a risk grading ([risk=medium]) not present in annotations, which is genuine added context, but it says nothing about failure modes, name-uniqueness constraints, or reversibility.

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?

The write/risk tag is front-loaded and the Args block is dense and scannable with no filler sentences. It is slightly longer than strictly needed because two of the arg notes restate schema defaults.

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 mutating tool with no output schema, the description covers all inputs, the operation's nature, and a risk level, while annotations cover the safety hints. Missing only secondary details such as idempotency behavior or error conditions, which is a minor gap.

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 0%, so the description carries the full burden, and it documents all five parameters with meaningful semantics: value provenance ('from cluster_list', 'from config'), purpose of vlan_id, and the omit-for-default behavior of target. Defaults for subnet_type and target duplicate the schema, but the provenance and intent notes go beyond it.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/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 ('Create a subnet on a cluster'), which is unambiguous against siblings like subnet_list, subnet_get, and subnet_delete. It does not explicitly name or route away from any sibling, but the verb+resource pairing is clear enough to select it.

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

Usage Guidelines3/5

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

There is no explicit when-to-use or when-not-to-use guidance, but the arg hints imply a prerequisite chain ('cluster_ext_id: Target cluster extId (from cluster_list)'), telling the agent it must resolve a cluster first. That is useful but partial; nothing says when this should be preferred over other subnet operations.

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