Skip to main content
Glama
vbr-write-mcp

vbr-write-mcp

by Aquatick

Delete Object

delete_object
Destructive

Remove a specified Veeam Backup & Replication object by kind and UUID, optionally deleting stored backups or uninstalling agents for supported object types.

Instructions

Remove a VBR object.

Kinds: job, managed_server, repository, scale_out_repository, proxy, mount_server, credentials, cloud_credentials, encryption_password, kms_server, protection_group, recovery_token, unstructured_data_server, entra_id_tenant, ad_domain, global_vm_exclusion, role, user, datastore_latency (not mount_server). Optional options are the DELETE query parameters: deleteBackups (repository, scale_out_repository - also deletes the backups stored there), uninstallEverything (protection_group - uninstalls agents). Use delete_backup for backups. Confirmed by 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": {
      "kind": "<kind>",
      "id": "<id>"
    },
    "name": "delete_object"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes
kindYes
optionsNo
confirm_tokenNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4/5.0
Behavior4/5

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

Annotations already flag destructiveHint=true and idempotentHint=false, but the description adds meaningful destruction scope: `deleteBackups` also deletes the backups stored on a repository, and `uninstallEverything` uninstalls agents. The closing "Confirmed by the server" hints at a confirmation step but is too terse to explain the `confirm_token` handshake, leaving a real behavioral gap for a destructive tool.

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?

Front-loads the purpose, then groups kinds and options compactly; the long kind list is justified because it mirrors the enum. The stray "(not `mount_server`)" trailing the `datastore_latency` entry reads as an artifact and briefly muddies which kind is excluded.

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?

Return values need not be covered since an output schema exists, and destruction side effects are well covered. For a destructive, non-idempotent mutation with an unexplained required-ish `confirm_token` and no permission or irreversibility statement, the description still leaves an agent short of what it needs to invoke safely.

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?

With 0% schema description coverage the description carries the full burden, and it does explain the `kind` enum and both `options` keys with their effects. However, `confirm_token` is never mentioned in either the schema or the description, and `id` semantics are only implied by the uuid format, so one of four parameters is entirely undocumented.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Opens with a specific verb+resource ("Remove a VBR object") and enumerates the exact kinds it operates on, which is far more precise than the title alone. It also explicitly routes backups to `delete_backup`, so the agent can distinguish it from the closest sibling without opening a schema.

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?

Gives one explicit alternative ("Use `delete_backup` for backups") and ties the two `options` keys to the specific kinds they apply to, which is real when-to-use guidance. It stops short of stating prerequisites — notably what `confirm_token` is for and whether a prior call is needed to obtain it — so the agent still has to guess at the invocation sequence.

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