Skip to main content
Glama
vbr-write-mcp

vbr-write-mcp

by Aquatick

Change Encryption Password

change_encryption_password
Destructive

Change an encryption password and its hint for backup jobs; new backups use the new password, while existing backups still require the old one to restore.

Instructions

Change an encryption password (and its hint). Jobs using it encrypt new backups with the new password; existing backups still need the old one to restore - keep it safe.

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": {
      "encryption_password_id": "<encryption_password_id>",
      "new_password": "<new_password>",
      "new_hint": "<new_hint>"
    },
    "name": "change_encryption_password"
  }
}

Input Schema

NameRequiredDescriptionDefault
new_hintYes
new_passwordYes
confirm_tokenNo
encryption_password_idYes

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 mark this as destructive and non-idempotent, and the description adds important detail about which backups are affected and why the old password must be retained. It still does not explain the confirm_token or broader authentication requirements, so it is strong but not complete.

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?

The definition is two sentences, front-loads the action, and uses the remainder for the critical backup-retention caveat. There is no unnecessary wording.

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?

The description covers the core mutation and an important backup consequence, and the output schema handles return values. However, for a destructive four-parameter tool with no schema descriptions, missing guidance on encryption_password_id and especially confirm_token leaves invocation details incomplete.

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 the description must carry parameter meaning. It clarifies that both a new password and new hint are involved, but it does not explain encryption_password_id or confirm_token, leaving two of four parameters undocumented.

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: changing an encryption password and its hint. It is clearly distinct from the sibling verify_encryption_password because it describes a mutation rather than verification.

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 gives clear operational context: jobs using the password will encrypt new backups with the new password, while existing backups still require the old password. It does not explicitly name alternatives such as verify_encryption_password or state prerequisites, so it stops short of a 5.

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