ppdm-mcp-server

restore_latest

Restores an asset to its original location from a recent backup copy in one call, without requiring manual copy browsing.

Instructions

Restore an asset to its original location from the most recent copy — single call, no manual copy browsing needed.

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

Input Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

First observedv4.2.2Nov 11, 2026

TDQS

B3.3/5.0

Behavior2/5

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

With no annotations, the description carries the full burden and leaves key behavior unstated: that restoring to the original location overwrites whatever is currently there, whether the operation is asynchronous and needs to be polled via get_restore_status or poll_until_complete, and what happens if the asset is in use. Only the "single call" convenience is disclosed.

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 the action and the source/destination highlighted, followed by the differentiator. The trailing "no manual copy browsing needed" is mildly promotional but earns its place as a usage cue.

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 tool with no output schema, the definition covers what it does and where the data comes from. The remaining gaps are behavioral (overwrite semantics, async tracking), not structural.

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?

The single parameter is fully documented in the schema (exact name or unique partial match), so the schema already does the work. The description adds nothing about matching behavior, ambiguity handling, or failure modes for the asset_name argument, which is the baseline expectation at 100% coverage.

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 concrete verb and resource ("restore an asset") plus the source of the data ("most recent copy") and the destination ("original location"), which is enough to distinguish it from siblings like cancel_restore or get_restore_status. It stops short of naming those siblings, so the differentiation is inferential 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?

The phrase "single call, no manual copy browsing needed" implies the intended use case — a quick restore without selecting a specific copy — but it never states when to choose this over browsing copies or how it relates to cancel_restore/get_restore_status. No prerequisites or exclusions are given.

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