Skip to main content
Glama
vbr-write-mcp

vbr-write-mcp

by Aquatick

Remove Installed License

remove_installed_license
Destructive

Removes the installed Veeam license, or only its Instance or Socket section, to stop jobs from processing unlicensed workloads after server confirmation.

Instructions

Remove the installed license (or only its Instance or Socket section). Jobs stop processing unlicensed workloads. Confirmed by the server.

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": "remove_installed_license"
  }
}

Input Schema

NameRequiredDescriptionDefault
sectionNoAll
confirm_tokenNo
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 declare destructiveHint=true, readOnlyHint=false and idempotentHint=false, so the safety profile is covered. The description adds real value beyond that by disclosing the operational consequence (jobs stop processing unlicensed workloads) and that the action is server-confirmed, but it never explains what confirm_token or force_standalone_mode do in a destructive flow.

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?

Three short sentences, zero waste: the action and its scope lead, the consequence follows, and the confirmation note closes. Nothing is repeated from the title or annotations.

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 not be described, and the destructive nature is covered by annotations plus the consequence sentence. However, for a destructive tool the unexplained confirm_token and force_standalone_mode parameters leave a real behavioral gap that the description should have closed.

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% across three parameters. The description only illuminates the 'section' parameter by naming its All / Instance / Socket variants; confirm_token and force_standalone_mode are left entirely unexplained in both schema and prose, which is a notable gap for a destructive operation.

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?

States a specific verb and resource ('Remove the installed license') and immediately scopes it with the parenthetical offering All / Instance / Socket granularity, which distinguishes it from install_license and manage_instance_license. It stops short of naming a sibling explicitly, so it is clear but not maximally differentiated.

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 consequence clause ('Jobs stop processing unlicensed workloads') implies why and when an operator would reach for this tool, but there is no explicit when-to-use / when-not-to-use guidance and no pointer to install_license or manage_instance_license as the alternative path.

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