Skip to main content
Glama
vbr-write-mcp

vbr-write-mcp

by Aquatick

Refresh License

refresh_license

Renew the installed Veeam license or fetch the current license state after a contract change. Sync licensing data with Veeam's server; internet access is required.

Instructions

renew: download the renewed license from Veeam for the installed one; update: fetch the current license state (e.g. after a contract change) from the Veeam licensing server. Needs internet access on 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": {
      "action": "<action>"
    },
    "name": "refresh_license"
  }
}

Input Schema

NameRequiredDescriptionDefault
actionYes
confirm_tokenNo
force_standalone_modeNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior3/5

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

Beyond the annotations, the description adds a real operational constraint (internet access required on the server) and reveals that the tool contacts an external Veeam licensing server, which is meaningful context for an outbound-dependent call. It does not state whether `renew` replaces/disables the currently installed license, whether services restart, or what confirmation `confirm_token` implies, so much of the mutation behavior remains undisclosed.

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 clauses plus a prerequisite sentence; each maps to an action or a constraint, with no filler. The backtick-formatted enum labels make the mapping scannable, though the prerequisite is appended last rather than front-loaded.

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 explained, and the action semantics are covered. However, for a license-mutating tool with a confirmation token and a mode-forcing flag, leaving those parameters and the side effects of `renew` undocumented is a notable completeness 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 description coverage is 0%, so the description carries full burden. It explains the `action` enum values well, but `confirm_token` and `force_standalone_mode` are never mentioned anywhere, leaving two of three parameters semantically opaque; partial compensation only.

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 specific verb+resource pairs for both modes: `renew` downloads the renewed license for the installed one, and `update` fetches current license state from the Veeam licensing server. This separates the two behaviors clearly, but it names no sibling (e.g. install_license or manage_instance_license), so a caller must infer the boundary with other license tools.

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 supplies concrete usage context per action, notably 'after a contract change' for `update`, and a hard prerequisite that the server needs internet access. It stops short of explicit when-not conditions or naming alternatives such as install_license for a fresh license, so guidance is clear but not complete.

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