Skip to main content
Glama
vbr-write-mcp

vbr-write-mcp

by Aquatick

Manage Instance License

manage_instance_license
Destructive

Assign a Server or Workstation instance license to a workload, or remove its license so it requires one again at the next backup.

Instructions

Assign an instance license to a workload as Server or Workstation, or remove the workload's instance license (it then needs a license again at the next backup).

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": {
      "instance_id": "<instance_id>",
      "action": "<action>"
    },
    "name": "manage_instance_license"
  }
}

Input Schema

NameRequiredDescriptionDefault
actionYes
instance_idYes
confirm_tokenNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true, idempotentHint=false and readOnlyHint=false, so the risk profile is known. The description adds genuinely useful consequence detail for the remove path (the workload will need a license again at the next backup), but it says nothing about how the assignment behaves when a license is already assigned, or what the mutation returns.

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?

A single front-loaded sentence that opens with the primary action and folds the destructive alternative in as a clause. Dense but every clause carries information; no filler or repetition.

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 the destructive annotation covers risk. However, for a three-parameter mutation with zero schema descriptions, the omission of confirm_token's role and any prerequisite or permission context leaves the definition short of complete.

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, so the description must carry the load. It partially explains the action enum by spelling out the Server/Workstation distinction and the remove semantics, but confirm_token is never mentioned even though it is a guard parameter the agent must decide whether to supply, and instance_id receives no elaboration.

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 concrete verb and resource ('Assign an instance license to a workload') plus the two license modes (Server/Workstation) and the removal variant, so the operation is unambiguous. It does not distinguish itself from near-siblings such as install_license, remove_installed_license, or set_license_options, which is the only thing keeping it from 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?

Usage is implied through the action alternatives rather than stated as guidance: the agent learns it may assign server, assign workstation, or remove, and that removal leaves the workload unlicensed until the next backup. There is no explicit when-to-use-this-instead-of-sibling-license-tool guidance and no stated preconditions (e.g. whether an existing license must be removed first).

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