Skip to main content
Glama
vbr-write-mcp

vbr-write-mcp

by Aquatick

Failover Replicas

failover_replicas
Destructive

Fail over VMware vSphere replica VMs to the disaster recovery site in now, planned, permanent, or undo mode, then complete the switch with failback or by making replicas permanent production VMs.

Instructions

VMware vSphere replica failover. Pass one replica point (restore point of a replica) per VM.

  • now: power the replicas on at the DR site (disaster: production is lost).

  • planned: last sync, shut production down, switch to the replicas (migration / expected outage).

  • permanent: make the replicas the permanent production VMs (no failback).

  • undo: discard the failover - replicas are powered off, their changes lost. After now/planned, finish with failback_replicas or failover_replicas(mode='permanent'|'undo').

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": {
      "mode": "<mode>",
      "replica_point_ids": "<replica_point_ids>"
    },
    "name": "failover_replicas"
  }
}

Input Schema

NameRequiredDescriptionDefault
modeYes
reasonNo
confirm_tokenNo
replica_point_idsYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already flag destructiveHint=true and readOnlyHint=false, and the description adds real consequence detail: 'planned' shuts production down, 'undo' powers replicas off and loses their changes, 'permanent' precludes failback. The notable omission is that confirm_token exists and is presumably required to authorize these destructive operations, which the description never mentions.

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?

A one-line purpose statement followed by a tight four-bullet mode table and a single closing sequencing sentence. No filler, and the critical mode semantics are front-loaded before the follow-up instruction.

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

Completeness3/5

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

Output schema exists so return values need no explanation, and mode behavior is well covered. But for a destructive, non-idempotent failover tool with 0% schema coverage, leaving confirm_token and reason unexplained means an agent lacks the full picture of what is required to invoke it successfully.

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?

With 0% schema description coverage, the description must carry the load, and it does fully explain the four 'mode' enum values, which is the highest-value parameter. However, 'reason' and 'confirm_token' are left entirely undefined in both schema and description, so half the parameters still have no semantic guidance.

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 opens with a specific verb and resource ("VMware vSphere replica failover") and immediately enumerates the four modes with their distinct outcomes. An agent can distinguish this from failback_replicas, which the description explicitly names as the counterpart operation.

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

Usage Guidelines5/5

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

Each mode is given a concrete triggering situation: 'now' for a disaster where production is lost, 'planned' for migration/expected outage, 'permanent' when no failback is wanted, 'undo' to discard. It also states the required follow-up path after now/planned, naming both failback_replicas and a failover_replicas call with permanent/undo.

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