Skip to main content
Glama
vbr-write-mcp

vbr-write-mcp

by Aquatick

Install License

install_license
Destructive

Install a Base64-encoded license file on a Veeam Backup & Replication server to replace the existing license, with server-side confirmation.

Instructions

Install a license file on the backup server, replacing the installed license. Confirmed by the server.

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": {
      "license_base64": "<license_base64>"
    },
    "name": "install_license"
  }
}

Input Schema

NameRequiredDescriptionDefault
confirm_tokenNo
license_base64YesThe .lic file content, Base64-encoded.
force_standalone_modeNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already flag this as a destructive, non-idempotent, non-read-only write. The description adds meaningful context beyond them by naming what is destroyed (the previously installed license) and that the server confirms the change. However it says nothing about irreversibility, whether the token workflow is required, or any server-restart/activation side effect.

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?

Two tight sentences, front-loaded with the action and immediately followed by its destructive consequence and confirmation behavior. Nothing is wasted or buried.

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 presence of an output schema means return values need not be explained, and the core action plus replacement semantics are covered. Still, for a destructive three-parameter licensing tool, it omits what confirm_token and force_standalone_mode do and gives no warning about reversibility, leaving an agent under-informed before invoking.

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 only license_base64 is documented there. The description mentions no parameters at all, so the purpose of confirm_token (a confirmation/undo token?) and force_standalone_mode is undocumented in both places — a significant gap the description should have filled.

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 states a specific verb and resource ('Install a license file on the backup server') plus the key effect ('replacing the installed license'), so an agent knows exactly what the operation does. It stops short of differentiating from close siblings such as manage_instance_license, refresh_license, or remove_installed_license, which the agent must resolve on its own.

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?

Usage is only implied: 'replacing the installed license' hints the tool is for swapping in a new .lic file, but there is no explicit when-to-use, when-not-to-use, or pointer to refresh_license/manage_instance_license as alternatives. Given several sibling tools deal with licensing, this leaves a real selection gap.

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