Skip to main content
Glama
Sign In
ppdm-mcp-server

ppdm-mcp-server

by Moodswing9
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

cancel_activity

Stops a running PowerProtect Data Manager activity by its activity ID, helping halt unwanted or stuck backup jobs and free resources.

Instructions

Cancel a running PPDM activity.

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": {
      "activity_id": "<activity_id>"
    },
    "name": "cancel_activity"
  }
}

Input Schema

NameRequiredDescriptionDefault
activity_idYesPPDM activity ID to cancel

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv4.2.2

TDQS

C2.9/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 burden. The word 'running' usefully implies only in-flight activities are eligible, but it says nothing about whether cancellation is graceful or forced, whether it is reversible, what permissions are needed, or what happens to partial work.

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?

One short, front-loaded sentence with no filler or redundancy. It is efficient, though the terseness borders on under-specification for a destructive mutation rather than being genuinely well-structured.

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?

The tool is simple (one required parameter, no nesting, no output schema), but it is a destructive mutation with zero annotation coverage. The description omits outcome, failure behavior, and permission context, leaving the agent to guess at the most consequential aspects of the call.

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 single activity_id parameter is already documented as the 'PPDM activity ID to cancel'. The description adds no format, sourcing, or lookup guidance beyond the schema, 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 and resource: cancel a running PPDM activity. The singular 'a running activity' implicitly contrasts with bulk operations like bulk_cancel_jobs, but no sibling is named, so the distinction is left to inference.

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?

No explicit when-to-use or when-not-to-use guidance. An agent cannot tell from the description whether cancel_restore, bulk_cancel_jobs, or pause_policy is the right call for a given situation, nor what prerequisites exist before cancelling.

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

Deploy Server

Other Tools