Skip to main content
Glama
vbr-write-mcp

vbr-write-mcp

by Aquatick

Change Credentials Secret

change_credentials_secret
Destructive

Rotate the secret in a Veeam credentials record so jobs, servers, guests, or cloud accounts use the new password or key on their next connection; use the correct value to avoid breaking them.

Instructions

Rotate the secret of a stored credentials record used by VBR to reach servers, guests or cloud accounts.

password (standard or Linux account), linux_root_password, linux_private_key (secret = the key, optional passphrase), cloud_secret_key (secret key of a cloud credentials record). Every job and server using the record uses the new secret from the next connection - a wrong value breaks them.

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": {
      "credentials_id": "<credentials_id>",
      "what": "<what>",
      "secret": "<secret>"
    },
    "name": "change_credentials_secret"
  }
}

Input Schema

NameRequiredDescriptionDefault
whatYes
secretYes
passphraseNo
confirm_tokenNo
credentials_idYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior4/5

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

Beyond the destructiveHint/readOnlyHint=false annotations, the description discloses the real blast radius: every job and server using the record picks up the new secret on the next connection, and a wrong value breaks them. That is genuine operational context annotations cannot express. It stops short of describing permission requirements or whether the prior secret is recoverable.

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 compact sentences, front-loaded with the action and its target, then the parameter mapping. The parenthetical enum breakdown is dense but each entry earns its place; nothing redundant.

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?

Return values need not be explained because an output schema exists, and the destructive consequence is covered. The missing piece is `confirm_token` on a destructive, non-idempotent operation - an agent cannot tell from the definition whether it must supply one or what it guards.

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?

With 0% schema description coverage the description does valuable work mapping the `what` enum values to what `secret` must contain (password, root password, private key + optional `passphrase`, cloud secret key). However, `credentials_id` and `confirm_token` are never explained, leaving two of five parameters undocumented anywhere.

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 and resource ('Rotate the secret of a stored credentials record') and immediately scopes it to VBR's use of that record to reach servers, guests, or cloud accounts. An agent can distinguish this from generic write siblings without opening the 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 description implies usage (rotate an existing record's secret) and warns of the consequence, but gives no explicit when-to-use versus when-not guidance, no prerequisites, and does not differentiate from the sibling change_encryption_password, which an agent could easily confuse with it.

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