Nutanix MCP Server

Overview Schema Source Related Servers Discussions Admin

generate_vm_report

Generate detailed As-Built reports for one or more VMs, covering configuration, compute, disks, NICs, categories, and host placement, with an optional Excalidraw diagram.

Instructions

Generate a detailed As-Built report for one or more VMs. Covers VM configuration, compute resources, disks, NICs, categories, and host placement. Returns Markdown with an Excalidraw VM layout diagram.

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": {
      "vm_uuids": "<vm_uuids>"
    },
    "name": "generate_vm_report"
  }
}

Input Schema

Name	Required	Description	Default
`vm_uuids`	Yes	List of VM UUIDs to report on (required).
`include_diagram`	No	Include Excalidraw VM diagram JSON (default: true)

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 are provided, so the description carries full responsibility. It discloses that the tool returns Markdown with an Excalidraw diagram, but does not state whether the operation is read-only, requires special authorization, has rate limits, or any potential side effects. The behavioral profile is minimal.

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 concise with two well-structured sentences. The first sentence states the purpose and scope, the second specifies the output format. No unnecessary words.

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?

Given the moderate complexity (generates a detailed report with a diagram) and lack of output schema, the description covers key aspects: what the report includes, the output format. It does not address error handling, limitations on VM count, or performance, but remains reasonably complete for typical usage.

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 coverage is 100% with clear descriptions for both parameters. The description adds context about the report's content (e.g., compute, disks, NICs), which helps understand the output but does not elaborate on parameter constraints or usage beyond the schema. Baseline 3 is appropriate.

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 clearly states the tool generates a detailed As-Built report for one or more VMs, covering configuration, compute, disks, NICs, categories, and host placement. This distinguishes it from sibling tools like generate_cluster_report or get_vm.

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?

The description provides no guidance on when to use this tool versus alternatives such as get_vm or generate_cluster_report. It does not specify prerequisites, context, or exclusions.

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