Skip to main content
Glama
vbr-write-mcp

vbr-write-mcp

by Aquatick

Unmount File Level Restore

unmount_file_level_restore

Unmount a file-level restore mount when you finish browsing or copying files, using the restore session ID to release the mount.

Instructions

Unmount a file-level-restore mount when you are done with it.

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": {
      "session_id": "<session_id>"
    },
    "name": "unmount_file_level_restore"
  }
}

Input Schema

NameRequiredDescriptionDefault
session_idYes
confirm_tokenNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, and openWorldHint=false, so the safety profile is partly covered. The description adds nothing beyond 'when you are done with it' – it does not say whether the restore session is terminated, whether mounted data is discarded, whether prior restored files persist, or how confirm_token affects the 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?

A single short, front-loaded sentence with no filler. It is efficient, though its brevity is part of why behavioral and parameter detail is missing.

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 values need not be described, and the lifecycle verb is clear. For a state-changing session-teardown call with two fully undocumented parameters, however, the definition leaves too much for the agent to infer from the schema alone.

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 0%, so both parameters depend on the description, yet the description explains neither session_id (which mount/session is targeted) nor confirm_token (when it is required and what it guards). Only an indirect hint that some existing mount is referenced is conveyed.

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 ('unmount a file-level-restore mount'), which is enough to distinguish it from the browse_file_level_restore and start_file_level_restore siblings by lifecycle stage. It stops short of explicitly naming those siblings or the session it acts on.

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?

'when you are done with it' gives an implied trigger condition but no explicit prerequisites (that the session must have been created by start_file_level_restore), no statement about consequences of leaving a mount open, and no alternatives to consider.

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