Skip to main content
Glama
vbr-write-mcp

vbr-write-mcp

by Aquatick

Set License Options

set_license_options

Updates Veeam Backup & Replication license settings, including automatic license updates, proactive support, and unlicensed agent instance consumption. Only specified options are changed.

Instructions

Switch license options: automatic license update (with proactive support) and instance consumption by unlicensed agents. Only the options you pass are changed.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "set_license_options"
  }
}

Input Schema

NameRequiredDescriptionDefault
auto_updateNo
confirm_tokenNo
proactive_supportNo
unlicensed_agent_consumptionNoLet unlicensed Veeam Agents consume instances from the license.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false and destructiveHint=false, so the safety profile is covered. The description adds the important non-obvious behavior that unspecified options are left untouched, preventing an agent from assuming a full overwrite. It says nothing about permissions, whether changes take effect immediately, or what confirm_token implies for a mutation.

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 sentences, front-loaded with the action and the affected options, then the partial-update rule. No filler, no restatement of the title.

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?

An output schema exists, so return values need no explanation, and annotations cover the read/write profile. Still, for a mutation tool with four parameters and only 25% schema coverage, the unexplained confirm_token and the absent permissions/effect-timing details leave a meaningful gap.

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 coverage is only 25% (only unlicensed_agent_consumption is documented inline), so the description carries real burden. It explains auto_update, proactive_support, and unlicensed_agent_consumption, but leaves confirm_token completely unexplained and does not clarify how auto_update and proactive_support interact, which the parenthetical 'with proactive support' only hints at.

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 specific verb ('Switch') plus the resource ('license options') and enumerates the three option families it controls: automatic license update/proactive support and instance consumption by unlicensed agents. That is enough to distinguish it from license install/refresh/remove siblings. It stops short of explicitly naming a sibling it is not, so a 4 rather than a 5.

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?

'Only the options you pass are changed' establishes partial-update semantics, which is genuinely useful when-to guidance. However, there is no statement of when to prefer this over install_license, manage_instance_license, or refresh_license, and no prerequisites or exclusions. Usage is implied rather than instructed.

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