ppdm-mcp-server

cancel_restore

Cancel a running PPDM restore session by ID to stop unwanted or stalled restore operations.

Instructions

Cancel a running PPDM restore session by ID

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": {
      "sessionId": "<sessionId>"
    },
    "name": "cancel_restore"
  }
}

Input Schema

Name	Required	Description	Default
`sessionId`	Yes	Restore session ID to cancel

Schema Changelog

Changes observed during successful MCP inspections.

First observedv4.2.2Nov 11, 2026

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. It does not say whether cancellation is reversible, what happens to partially restored data, what permissions are needed, or what error occurs if the session is not running — significant gaps for a destructive operation.

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 front-loaded sentence with no wasted words; it is terse but not truncated, and the scope qualifier 'running' is placed before the identifier detail.

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?

For a single-parameter tool with no output schema this is close to sufficient, but an agent still lacks confirmation of side effects, irreversibility, and behavior on a non-running session.

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% with a single required sessionId already described as 'Restore session ID to cancel'. The description's 'by ID' adds nothing beyond that, 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 restore session, identified by ID. This distinguishes it from job/activity cancellers among siblings, though it never names those alternatives explicitly.

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 word 'running' implies the session must be active, but there is no explicit when-to-use guidance, no mention of alternatives such as cancel_activity or bulk_cancel_jobs, and no prerequisites or failure conditions described.

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