ppdm-mcp-server

pause_policy

Pause a PowerProtect Data Manager protection policy to stop scheduled backup jobs from running until you resume it. Specify the exact policy name or a unique partial match.

Instructions

Disable (pause) a PPDM protection policy — jobs will not run until resumed.

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>"
    },
    "name": "pause_policy"
  }
}

Input Schema

Name	Required	Description	Default
`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

A3.6/5.0

Behavior3/5

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

With no annotations, the description carries the full burden, and it does disclose the key consequence: jobs will not run while paused, and the change is reversible via resume. It omits other relevant behavior such as required permissions, whether already-running jobs are affected, or what the call returns on success.

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?

One compact sentence with the action front-loaded and the operational consequence attached. Nothing is wasted and nothing important is buried.

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

Completeness4/5

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

For a one-parameter state-toggle with no output schema, the definition gives enough to call it correctly: the target resource and the effect on jobs. Only minor gaps remain around permissions and the response shape.

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 coverage is 100% for the single parameter, and the schema itself already explains the exact-or-unique-partial-name matching rule. The description adds no additional meaning about policy_name, so the baseline 3 applies.

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?

States a specific verb pair ('Disable (pause)') and a specific resource ('a PPDM protection policy'), so the agent knows exactly what changes. The trailing clause 'until resumed' gestures at the sibling resume_policy without naming it, so differentiation is implicit rather than explicit.

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?

Usage is only implied: the agent can infer this is the tool for halting policy-driven jobs, and 'until resumed' hints that resume_policy reverses it. There is no explicit when-to-use, when-not-to-use, or prerequisite statement (e.g., maintenance windows, permission requirements).

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