ppdm-mcp-server

trigger_backup

Triggers an on-demand backup for a specified asset using a named protection policy, enabling immediate protection when scheduled backups are insufficient.

Instructions

Trigger an on-demand backup for an asset using a named protection policy.

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": {
      "policy_name": "<policy_name>",
      "asset_name": "<asset_name>"
    },
    "name": "trigger_backup"
  }
}

Input Schema

Name	Required	Description	Default
`asset_name`	Yes	Asset name — exact, or a partial name that matches only one asset
`policy_name`	Yes	Policy name — exact, or a partial name that matches only one policy

Schema Changelog

Changes observed during successful MCP inspections.

First observedv4.2.2Nov 11, 2026

TDQS

B3.1/5.0

Behavior2/5

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

No annotations are supplied, so the description carries the full disclosure burden for a state-changing action. It does not say whether the call is synchronous or returns a job identifier, what permissions are required, whether it fails on an already-running job, or what errors look like on partial-name ambiguity.

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 with zero filler, stating verb, target, and required policy up front. Its brevity is efficient, though it borders on under-specification rather than excess.

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 an action tool with no annotations and no output schema, the definition leaves important operational questions unanswered: whether a backup job id is returned, whether the call blocks, and how failures surface. The well-covered input schema partly compensates, but the behavioral picture remains thin.

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?

Schema description coverage is 100%, and the schema already explains both the exact-match and unique-partial-match semantics for each parameter. The description only echoes that a policy name and asset name are involved, adding no syntax, format, or disambiguation rules beyond the schema.

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 (trigger) and resource (an on-demand backup) scoped to a single asset and a named protection policy. The singular 'for an asset' implies single-target behavior, though the definition never explicitly distinguishes itself from the sibling bulk_trigger_backup.

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 phrase 'on-demand' implies a contrast with scheduled backups, giving implied usage context, but there is no explicit when-to-use guidance, no stated prerequisites, and no mention of alternatives such as the bulk variant or cancel/restore tools.

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