Skip to main content
Glama
vbr-write-mcp

vbr-write-mcp

by Aquatick

Apply Job Configuration

apply_job_configuration

Push a Veeam Agent backup policy’s current configuration to its managed agents to apply policy changes. Use only for agent backup and workstation policy job types.

Instructions

Push a Veeam Agent backup policy's current configuration to the agents it manages ("Apply configuration").

Only for agent backup policies (*AgentBackupServerPolicy / *WorkstationPolicy job types).

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": {
      "job_id": "<job_id>"
    },
    "name": "apply_job_configuration"
  }
}

Input Schema

NameRequiredDescriptionDefault
job_idYes
confirm_tokenNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.3/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 description carries a lighter burden. It adds the meaningful disclosure that the effect is pushing a stored policy config outward to managed agents, but it doesn't say what happens to agents that are offline, whether the operation is idempotent, or whether confirm_token is required for it.

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?

Two short sentences, with the core action stated first and the applicability constraint second. No padding, no restatement of the title beyond mapping to the UI label.

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-value explanation isn't required, and the annotations cover the safety profile. Still, for a mutation tool with 0% schema coverage, the definition leaves the confirmation parameter and any preconditions (agent connectivity, policy type validation) undocumented.

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% for two parameters, so the description would need to explain job_id and confirm_token itself. Neither is mentioned; in particular, the presence of an unexplained confirm_token parameter leaves the agent guessing at the confirmation semantics of a mutating call.

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 states a specific verb and resource: push a Veeam Agent backup policy's current configuration to the agents it manages, and maps that to the UI label "Apply configuration". The job-type restriction narrows the scope but the case doesn't explicitly contrast with siblings such as export_configuration or api_write, leaving the agent to reason about the difference.

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?

The line 'Only for agent backup policies (`*AgentBackupServerPolicy` / `*WorkstationPolicy` job types)' gives a clear applicability gate and implies usage whenever a policy of that type needs its config propagated. However, it never states when NOT to use it or which sibling to reach for instead when the job is not an agent policy.

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