Nutanix MCP Server

Overview Schema Source Related Servers Discussions Admin

list_subnets

Retrieve subnets/VLANs configured in Prism Central including names, VLAN IDs, CIDRs, IP pools, and associated clusters. Supports filtering by name or VLAN ID and limiting results.

Instructions

List subnets/VLANs configured in Prism Central. Returns subnet names, VLAN IDs, CIDRs, IP pools, and associated clusters.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_subnets"
  }
}

Input Schema

Name	Required	Description	Default
`filter`	No	OData filter expression. Examples: "name eq 'production-vlan'", "vlanId eq 100"
`limit`	No	Maximum number of subnets to return. Omit to retrieve all (auto-paginates).

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0May 7, 2026

TDQS

B3.4/5.0

Behavior2/5

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

No annotations provided; description only states return values but omits behavioral details such as pagination, auth requirements, or rate limits.

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 efficiently conveys purpose and output, with no redundant text.

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?

Lists return fields adequately for a read-only operation, but lacks mention of error conditions or performance characteristics.

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?

Input schema already has 100% description coverage for both parameters, so description adds marginal value beyond stating return fields.

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 explicitly states the tool lists subnets/VLANs in Prism Central and enumerates return fields, distinguishing it from sibling tools like get_subnet.

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 vs alternatives, or when to apply filter vs no filter.

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