Skip to main content
Glama
vbr-write-mcp

vbr-write-mcp

by Aquatick

Restore Hyperv Vm

restore_hyperv_vm
Destructive

Restores a Microsoft Hyper-V VM from a restore point either in place or to a chosen host, with optional new name, storage, and network mapping.

Instructions

Full restore of a Microsoft Hyper-V VM. OriginalLocation overwrites the VM in place; Customized restores to destination_host (and optionally a new name, storage and network mapping - see describe_model for HvRestoreTargetDatastoresSpec / HvRestoreTargetNetworkSpec / HvRestoreTargetNameSpec).

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": "restore_hyperv_vm"
  }
}

Input Schema

NameRequiredDescriptionDefault
modeYes
reasonNo
networkNoCustomized: HvRestoreTargetNetworkSpec.
new_nameNo
power_upNo
datastoreNoCustomized: HvRestoreTargetDatastoresSpec.
confirm_tokenNo
secure_restoreNoOptional SecureRestoreSpec: {'antivirusScanEnabled': bool, 'yaraScanEnabled': bool, 'yaraRule': str, 'virusDetectionAction': 'AbortRecovery'|'DisableNetwork'|'Ignore', 'entireVolumeScanEnabled': bool}.
destination_hostNoCustomized: HyperVObjectModel of the target host/cluster.
restore_point_idYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true, readOnlyHint=false and idempotentHint=false, so the safety profile is covered. The description adds real value by stating that `OriginalLocation` overwrites the VM in place while `Customized` writes to `destination_host`, but says nothing about confirm_token, power_up, secure_restore scanning, or failure/partial-restore behavior on 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 sentences with no filler, and the mode split is presented before the optional sub-specs. Slightly dense with backticked identifiers, but every clause carries 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?

A destructive 10-parameter restore with an output schema needs less return-value explanation, and describe_model delegation covers the nested specs. However, the mode-conditional requirements for the remaining parameters and the role of confirm_token on a destructive restore are not addressed, leaving gaps an agent could stumble on.

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 10 parameters at only 40% schema description coverage, the description compensates for the mode-dependent ones (mode, destination_host, new_name, datastore, network) and correctly notes the latter three apply only to Customized. It leaves `reason`, `power_up`, `confirm_token` and `secure_restore` entirely to the schema, where some have no description at all.

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 and resource ("Full restore of a Microsoft Hyper-V VM") and immediately distinguishes the two operating modes by name, so an agent can tell this apart from the instant-recovery siblings listed.

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

Usage Guidelines3/5

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

Explains the meaning of the two modes and points to `describe_model` for the spec shapes, which is useful routing. It does not say when this tool should be chosen over `start_instant_recovery_hyperv_vm` / `finish_instant_recovery_hyperv_vm` or `restore_cloud_director_vm`, so a full restore vs. instant recovery decision is left to inference.

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