Skip to main content
Glama
AIops-tools

Nutanix AIops

by AIops-tools
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

pd_failover

Destructive

Fail a protection domain over to a target cluster for disaster recovery. Preview the operation with dry_run before executing this high-risk event.

Instructions

[WRITE][risk=high] Fail a protection domain over to a target cluster (DR event).

Destructive DR operation; pass dry_run=True to preview. Tagged risk=high
(audit tier 'review'); NUTANIX_AUDIT_APPROVED_BY / NUTANIX_AUDIT_RATIONALE
optionally annotate who/why.

Args:
    policy_ext_id: Protection policy extId as returned by protection_domain_list.
    cluster_ext_id: Target cluster extId (from cluster_list).
    dry_run: If True, preview the failover without performing it.
    target: Prism Central target name from config; omit for the default.

Input Schema

NameRequiredDescriptionDefault
targetNo
dry_runNo
policy_ext_idYes
cluster_ext_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.7/5.0
Behavior5/5

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

Annotations declare destructive/readOnly/idempotent profile, and the description adds substantial context beyond them: the risk=high tag, audit tier 'review', the optional NUTANIX_AUDIT_APPROVED_BY / NUTANIX_AUDIT_RATIONALE approval annotation fields, and the dry_run preview path. This is exactly the richer behavioral detail the annotations cannot convey.

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-loads the [WRITE][risk=high] signal, then purpose, then a clean Args block. Slight redundancy between '[risk=high]' and 'Tagged risk=high', but otherwise tight and well-structured.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a high-risk mutation with no output schema, the description covers safety profile, preview mechanism, audit-approval metadata, and all parameter sourcing. Nothing an agent needs to invoke it correctly is missing.

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 coverage is 0%, so the description carries the full parameter burden and does so well: it explains each of the four params and, critically, names the source endpoint for the extIds (protection_domain_list, cluster_list) and that target is a Prism Central name from config defaulting when omitted.

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 (fail over) and resource (protection domain) plus the target (cluster) and frames it as a DR event. An agent can cleanly distinguish it from siblings like protection_domain_list, vm_protect, and snapshot_restore without opening any schema.

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?

Gives the operative usage condition: it is a destructive DR operation and dry_run=True previews it before executing. It does not name a specific alternative sibling tool for the non-failover case, so it stops short of explicit when-not guidance.

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

Deploy Server

Other Tools