Veeam VBR v13 MCP Server

DeleteCloudCredsHelperApplianceAsync

Remove a helper appliance from cloud credentials in Veeam Backup & Replication v13 to manage access and security.

Instructions

Remove a helper appliance from a cloud credentials record.

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": {
      "id": "<id>",
      "applianceId": "<applianceId>"
    },
    "name": "DeleteCloudCredsHelperApplianceAsync"
  }
}

Input Schema

Name	Required	Description	Default
`id`	Yes
`applianceId`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Apr 21, 2026

TDQS

C2.8/5.0

Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states 'Remove' (implying a destructive mutation) but fails to detail critical aspects like required permissions, whether the removal is reversible, side effects on the cloud credentials record, or error conditions. This is a significant gap for a mutation tool.

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?

The description is a single, efficient sentence with zero wasted words. It is front-loaded with the core action and target, making it easy to parse quickly.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a destructive mutation tool with no annotations, 0% schema coverage, and no output schema, the description is inadequate. It lacks essential details about behavior, parameters, outcomes, and error handling, leaving too many gaps for reliable tool invocation.

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 schema provides no parameter documentation. The description mentions 'a helper appliance' and 'a cloud credentials record', which loosely map to 'applianceId' and 'id', but it doesn't explain what these IDs represent, their format, or where to obtain them. This adds minimal value beyond the schema's structure.

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 clearly states the action ('Remove') and target ('a helper appliance from a cloud credentials record'), providing a specific verb+resource combination. It distinguishes itself from siblings like 'CreateCloudCredsHelperAppliance' by focusing on deletion, though it doesn't explicitly contrast with other deletion tools like 'DeleteCloudCreds'.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description offers no guidance on when to use this tool versus alternatives, prerequisites, or contextual constraints. It lacks any mention of when-not-to-use scenarios or explicit references to sibling tools, leaving usage entirely implicit.

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

Deploy Server