Skip to main content
Glama
vbr-write-mcp

vbr-write-mcp

by Aquatick

Finish Instant Recovery Hyperv Vm

finish_instant_recovery_hyperv_vm
Destructive

Completes a Hyper-V Instant Recovery by migrating the mounted VM to production storage or unmounting it, which discards all changes made inside the recovered VM.

Instructions

Finish a Hyper-V Instant Recovery mount: migrate the running VM to production storage, or unmount (tear it down; changes made inside the recovered VM are lost). Mount ids: api_read('/api/v1/restore/ instantRecovery/hyperV/vm').

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": {
      "mount_id": "<mount_id>",
      "action": "<action>"
    },
    "name": "finish_instant_recovery_hyperv_vm"
  }
}

Input Schema

NameRequiredDescriptionDefault
actionYes
mount_idYes
confirm_tokenNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and idempotentHint=false, so the safety profile is partly covered. The description adds genuinely new context: that `unmount` discards changes made inside the recovered VM, and where mount ids come from. It omits any mention of `confirm_token`, which is a notable gap 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.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences, front-loaded with the core purpose, with the destructive consequence parenthesized right where it matters. No filler or restatement of the title.

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 destructive semantics are disclosed. The only real omission is the role and requirement of `confirm_token` on a destructive, non-idempotent operation.

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 description coverage is 0%, so the description must carry the load. It explains both enum values of `action` and gives a discovery path for `mount_id`, but `confirm_token` is never mentioned, leaving one of three parameters with no meaning beyond its name and type.

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 (finish) and resource (Hyper-V Instant Recovery mount), then enumerates the two terminal actions with their distinct outcomes. An agent can tell exactly what this tool does and how the two modes differ without opening the 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?

The description makes the choice between `migrate` and `unmount` explicit by giving the consequence of each (move to production storage vs. tear down and lose in-VM changes). It does not name a sibling tool or state prerequisites, but the action-level guidance is clear enough to select correctly.

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