Skip to main content
Glama
vbr-write-mcp

vbr-write-mcp

by Aquatick

Browse File Level Restore

browse_file_level_restore
Read-onlyIdempotent

Lists folders or searches within a mounted file-level-restore session to locate files and directories before restoring them. Read-only.

Instructions

List a folder (or search) in a file-level-restore mount. Read-only.

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>",
      "path": "<path>"
    },
    "name": "browse_file_level_restore"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathYesFolder in the mounted guest, e.g. 'C:\\' or '/etc'.
skipNo
limitNo
searchNoIf set, search below `path` for this name pattern.
item_typesNo
session_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.7/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the trailing 'Read-only.' merely restates structured data rather than adding context. The description says nothing about pagination behavior beyond the default limit, whether results are truncated, or what an exhausted browse implies.

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 short sentences, front-loaded with the primary action and with the search alternative placed immediately after. The only waste is the redundant 'Read-only.' tag, which duplicates the annotations.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a six-parameter, paginated browse tool with no output schema and low schema description coverage, the definition is too thin. An agent is left guessing at pagination semantics, item_types filtering, and how the search mode differs from plain listing.

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 33%, and the description only echoes the two parameters the schema already documents (path and search). It adds no meaning for skip, limit, item_types, or session_id, leaving most of the parameter surface unexplained in both places.

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?

The description gives a concrete verb and resource ('List a folder ... in a file-level-restore mount') plus the search variant, so an agent can tell it apart from restore_files or the start/unmount siblings. It stops short of naming any sibling, but the scope is unambiguous.

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

Usage Guidelines2/5

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

There is no when-to-use guidance: nothing says this must follow start_file_level_restore, that a session_id must reference a live mount, or when to prefer browsing over restoring files directly. The phrase 'in a file-level-restore mount' only hints at the prerequisite.

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