Skip to main content
Glama
vbr-write-mcp

vbr-write-mcp

by Aquatick

Start File Level Restore

start_file_level_restore

Mount a machine restore point to browse and restore individual guest files, returning a session ID for follow-up browse, restore, and unmount actions without altering production data.

Instructions

Mount a machine restore point for guest file-level restore (FLR). Returns the mount session; its id is the session_id for browse_file_level_restore, restore_files and unmount_file_level_restore.

Mounting changes nothing in production. Linux FLR uses a helper appliance/host configured in VBR.

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>",
      "guest_os": "<guest_os>"
    },
    "name": "start_file_level_restore"
  }
}

Input Schema

NameRequiredDescriptionDefault
reasonNo
guest_osYes
confirm_tokenNo
restore_point_idYes
auto_unmount_minutesNoUnmount after this much inactivity.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4/5.0
Behavior4/5

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

Annotations declare readOnlyHint=false, destructiveHint=false, openWorldHint=false, which is a modest bar, and the description adds real context beyond it: mounting changes nothing in production, a session is created, and Linux FLR depends on pre-configured VBR infrastructure. It omits operational details an agent might want, such as what happens to orphaned mounts or what the auto-unmount default means in practice.

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 short paragraphs, front-loaded with the action and followed by the session-id handoff and one prerequisite note. Every sentence carries information; nothing is redundant or buried.

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?

An output schema exists, so return-shape explanation is not owed, and the description does name the key returned value (session_id). However, for a 5-parameter mutation tool with 20% schema coverage, the undocumented confirm_token and reason parameters leave an agent guessing about confirmation requirements before invoking it.

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

Parameters2/5

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

Schema description coverage is only 20% — only auto_unmount_minutes is documented. The description adds no meaning for restore_point_id, guest_os, reason, or especially confirm_token, whose presence suggests a confirmation flow the description never explains (and whose necessity is muddied by the 'changes nothing in production' claim). With this low coverage the description had to compensate and does not.

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 states a specific verb and resource — 'Mount a machine restore point for guest file-level restore (FLR)' — and immediately frames it as the entry point whose session id feeds browse_file_level_restore, restore_files and unmount_file_level_restore. An agent can distinguish it from those siblings without opening any 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?

It clearly establishes the workflow position: call this first, then use the returned session_id with the browsing, restore and unmount tools. It also flags the Linux prerequisite (helper appliance/host configured in VBR). It stops short of explicit when-not-to-use guidance or a note on when a plain restore_files without browsing suffices.

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