Skip to main content
Glama
vbr-write-mcp

vbr-write-mcp

by Aquatick

Manage Move Copy Session

manage_move_copy_session
Destructive

Resolve a pending backup move/copy session by selecting Retry to retry failed parts, ForgetFailed to keep moved data, or StopAndUndo to roll back.

Instructions

Resolve a backup move/copy session that is waiting for a decision: Retry the failed part, ForgetFailed (keep what moved, drop the rest) or StopAndUndo (roll back).

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>",
      "action": "<action>"
    },
    "name": "manage_move_copy_session"
  }
}

Input Schema

NameRequiredDescriptionDefault
actionYes
session_idYes
confirm_tokenNo

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 already flag destructiveHint=true and idempotentHint=false, but the description adds real value by spelling out the consequence of each destructive choice: ForgetFailed keeps transferred data and drops the remainder, StopAndUndo rolls back. What is missing is the confirmation/auth requirement implied by confirm_token and whether resolution is synchronous.

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?

A single front-loaded sentence that names the precondition first, then the options, with each action glossed inline in parentheses. No redundant restatement of the title or name.

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 trade-offs are all covered. The remaining gap is procedural: when a confirm_token is needed and what state the session ends in after each action, which matters for a high-risk 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% across three parameters, so the description must carry the load. It explains the action enum values thoroughly, but session_id is left as self-evident and confirm_token — the security-relevant parameter with a null default — is never mentioned, so coverage is only partial.

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 ('Resolve') and resource ('backup move/copy session') with a qualifying condition ('waiting for a decision'), then enumerates the three outcomes it can produce. An agent can distinguish this from copy_backups / move_backup (which initiate transfers) 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 Guidelines3/5

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

The phrase 'session that is waiting for a decision' implies the precondition for calling it, which is genuinely useful context. However, it never states a when-not case, does not mention inspecting state first (e.g., via get_session_result) before choosing an action, and gives no guidance on the confirm_token parameter.

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