Skip to main content
Glama
vbr-write-mcp

vbr-write-mcp

by Aquatick

Start Instant Recovery Hyperv Vm

start_instant_recovery_hyperv_vm
Destructive

Start an Instant Recovery for a Microsoft Hyper-V VM by running it directly from a backup without a full data copy. Publish in place, on a target host, or recover other-platform backups.

Instructions

Instant Recovery to Microsoft Hyper-V: run the VM straight from the backup, without a full data copy.

OriginalLocation publishes it in place of the original; Customized on destination_host; OtherPlatform recovers a VMware/agent/other backup onto Hyper-V (needs destination_host). Finish with finish_instant_recovery_hyperv_vm (migrate to production or unmount).

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": {
      "restore_point_id": "<restore_point_id>",
      "mode": "<mode>"
    },
    "name": "start_instant_recovery_hyperv_vm"
  }
}

Input Schema

NameRequiredDescriptionDefault
modeYes
reasonNo
networkNo
new_nameNo
power_upNo
datastoreNo
confirm_tokenNo
secure_restoreNoOptional SecureRestoreSpec: {'antivirusScanEnabled': bool, 'yaraScanEnabled': bool, 'yaraRule': str, 'virusDetectionAction': 'AbortRecovery'|'DisableNetwork'|'Ignore', 'entireVolumeScanEnabled': bool}.
destination_hostNoHyperVObjectModel of the target.
restore_point_idYes
share_credentials_idNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the safety profile is known. The description adds genuinely useful lifecycle context beyond that: the VM runs from backup and is not finalized until finish_instant_recovery_hyperv_vm is called, and OriginalLocation overwrites the original's place. It still says nothing about resource consumption, permissions, or what an unfinalized session leaves behind.

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?

Short and front-loaded, with the core concept first and the mode semantics second. The telegraphic fragments ('`Customized` on `destination_host`') are compact but border on cryptic, and the closing workflow note is somewhat run-on.

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?

An output schema exists, so return values need no explanation, and the description covers the two hardest things an agent must get right: mode selection and the mandatory finish step. For an 11-parameter destructive operation it is thin on the remaining parameters and on failure/abort behavior, which is why it falls short of full completeness.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is only 18% across 11 params, so the description carries real weight: it defines the three mode enum values and the conditional dependency of destination_host, which is the single most error-prone parameter decision here. The remaining params (power_up, network, new_name, datastore, confirm_token, share_credentials_id, reason) get no mention, so it does not fully compensate for the coverage gap.

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?

Names a concrete verb and resource with the defining characteristic front-loaded: 'run the VM straight from the backup, without a full data copy'. That is exactly what separates it from a full restore sibling, though it never names restore_hyperv_vm as the alternative. The three mode names further pin down the operation's scope.

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 explicit per-mode routing: OriginalLocation for in-place publish, Customized on destination_host, OtherPlatform for VMware/agent backups onto Hyper-V with a stated destination_host requirement. It also names the required follow-up tool. Missing is any statement of when an agent should prefer this over a conventional restore, or any precondition/exclusion.

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