Nutanix MCP Server

Overview Schema Source Related Servers Discussions Admin

get_subnet

Retrieve detailed subnet configuration including IP pools, DHCP settings, and virtual switch assignment for a specified subnet UUID.

Instructions

Get detailed subnet configuration including IP pools, DHCP config, and virtual switch assignment.

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": {
      "subnet_uuid": "<subnet_uuid>"
    },
    "name": "get_subnet"
  }
}

Input Schema

Name	Required	Description	Default
`subnet_uuid`	Yes	The UUID (extId) of the subnet

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0May 7, 2026

TDQS

A3.6/5.0

Behavior3/5

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

No annotations provided. Description implies a read operation but does not disclose any behavioral traits (e.g., non-destructive, required permissions). Adequate for a simple getter but could be more explicit.

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?

Single sentence, front-loaded with purpose, concise and to the point.

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 simple getter with one parameter and no output schema, the description adequately explains what is retrieved. Lacks mention of related tools or error conditions, but sufficient for basic use.

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

Parameters3/5

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

Schema provides full coverage for the single parameter. Description adds no extra semantics to the parameter beyond what the schema already offers.

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?

Description clearly states 'Get detailed subnet configuration' and lists specific components (IP pools, DHCP config, virtual switch assignment). It distinguishes itself from sibling tools like get_vm or list_subnets.

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

Usage Guidelines2/5

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

No guidance on when to use this tool versus alternatives like list_subnets (which likely returns all subnets). No when-not or context provided.

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