Skip to main content
Glama
vbr-write-mcp

vbr-write-mcp

by Aquatick

Clone Role

clone_role

Create a copy of an existing custom Veeam Backup & Replication role, then adjust the duplicate with update_object(kind='role', ...) to set its permissions.

Instructions

Clone a custom role; adjust the copy with update_object(kind='role', ...).

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": {
      "role_id": "<role_id>"
    },
    "name": "clone_role"
  }
}

Input Schema

NameRequiredDescriptionDefault
role_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 readOnlyHint=false, destructiveHint=false, and openWorldHint=false, so the safety profile is covered and the description doesn't need to repeat it. The description does add one real behavioral fact: the clone is not final and is intended to be modified via update_object. It says nothing about what is copied (permissions, assignments), naming/collision behavior, or why a confirm_token exists on a non-destructive operation.

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 tight sentence with the operation front-loaded and the follow-up action second; nothing is padded. The inline call syntax is slightly cryptic out of context, but it is compact and actionable.

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 the description reasonably omits return values. For a mutation tool with an undocumented confirm_token and no statement of what a clone actually inherits, though, an agent could still call it correctly only by trial. It is minimally sufficient rather than 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%, so the description carries the full burden for both parameters and largely drops it. 'role_id' is inferable from 'clone a custom role', but 'confirm_token' — an unusual parameter on a non-destructive operation, defaulting to null — is never explained, leaving the agent to guess whether it is required in some deployments.

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 names a specific verb and resource ('Clone a custom role'), which is enough for an agent to distinguish it from the many update_/create_/delete_ siblings. It also scopes the operation to custom roles, implying system roles are not eligible. It stops short of saying how the clone differs from clone_job, but the resource name itself does that work.

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?

It supplies a useful follow-up instruction — use update_object(kind='role', ...) to adjust the copy — which tells the agent this tool is a starting point rather than a finish line. There is no guidance on prerequisites (permissions, whether the source role must exist) or on what conditions would make an agent pick clone_job instead. Usage context is implied rather than stated.

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