Skip to main content
Glama
vbr-write-mcp

vbr-write-mcp

by Aquatick

Failback Replicas

failback_replicas
Destructive

Fail back failed-over vSphere replicas by starting synchronization to an original, re-created, or custom target, then committing or undoing the failback and setting switchover timing.

Instructions

Failback of failed-over vSphere replicas, in steps:

  1. start - sync replica changes back to target (OriginalVM: the original VM, OriginalLocation: re-create it where it was, Customized: elsewhere). switchover decides when production takes over (Auto, Manual then switch_to_production, or Scheduled; change it later with change_switchover_time).

  2. commit - finalize; or undo - return to the failed-over state.

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": {
      "action": "<action>",
      "replica_point_ids": "<replica_point_ids>"
    },
    "name": "failback_replicas"
  }
}

Input Schema

NameRequiredDescriptionDefault
actionYes
targetNoaction='start': where to fail back to.
customizedNotarget='Customized': extra ViVMSnapshotReplicaCustomizedFailbackSpec fields - destinationhost, resourcePool, datastore, folder, network (see describe_model).
switchoverNoReplicaFailbackModeSpec {'type': 'Auto'|'Manual'|'Scheduled', 'scheduledTime': ISO-8601}.
confirm_tokenNo
dr_site_proxy_idsNo
replica_point_idsYes
power_on_target_vmNo
production_site_proxy_idsNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already flag destructiveHint=true and non-idempotent, and the description adds genuinely useful behavior: that undo reverts to the failed-over state, that commit is final, and that switchover timing is mutable after start. It does not disclose the confirm_token confirmation flow or proxy requirements, which matters for a destructive operation.

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?

Two front-loaded, step-numbered blocks with no filler; the action names are backticked so they map directly to enum values. Slightly dense parentheticals, but every sentence carries workflow information.

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?

Return values need not be explained because an output schema exists, and the action workflow is covered. For a destructive, nine-parameter tool, though, the confirmation token and site-proxy parameters are unexplained, leaving an agent without the full picture of how to complete a safe call.

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 only 33%, and the description does explain the two highest-risk parameters well: all five action values and the three target values (OriginalVM, OriginalLocation, Customized) plus switchover types. However, confirm_token, dr_site_proxy_ids, production_site_proxy_ids, power_on_target_vm, and the customized object are left entirely to the schema, so compensation is partial.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Failback of failed-over vSphere replicas') and enumerates the action lifecycle, so an agent knows exactly what domain this covers. It does not explicitly contrast with the sibling failover_replicas, but 'failed-over' and 'failback' make the inverse relationship inferable.

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?

The numbered step structure gives real sequencing guidance: start first, then either commit to finalize or undo to return to the failed-over state, and change_switchover_time to adjust timing later. What is missing is when to prefer this over failover_replicas or a general api_write call, and there is no 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.