ppdm-mcp-server

nw_list_savesets

List NetWorker backup copies and filter savesets by client hostname to quickly locate backups for a specific system.

Instructions

List NetWorker savesets (backup copies). Filter by client name.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "nw_list_savesets"
  }
}

Input Schema

Name	Required	Description	Default
`limit`	No	Max results (default 30)
`client_name`	No	Filter by client hostname substring

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?

With no annotations supplied, the description carries the full behavioral burden, and it discloses almost nothing beyond the basic action. It does not state that the call is read-only, whether results are sorted, what a result row contains, or that the default result set is truncated at 30 — all behavioral facts an agent needs to avoid misinterpreting a short list as exhaustive.

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?

Two short sentences, front-loaded with the action and resource, with zero filler. The only mild inefficiency is that the second sentence duplicates what the schema already says about client_name.

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 two-parameter, optional-argument list tool with full schema coverage and no output schema, the definition is minimally viable but thin. Because there is no output schema, the description should at least sketch what a saveset record contains and note the default-30 truncation, which it omits.

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%, so both parameters (limit with its default of 30, and client_name as a hostname substring filter) are already documented in the schema. The description's mention of client-name filtering adds no syntax, matching, or pagination detail beyond what the schema provides, 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?

Names a specific verb and resource ("List NetWorker savesets") and clarifies the domain term with "(backup copies)". It stops short of distinguishing the tool from the nearby nw_list_failed_savesets sibling, so an agent must infer that this one returns all savesets rather than a filtered subset.

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 only usage-like statement is "Filter by client name," which is really a restatement of the parameter rather than guidance on when to call this versus nw_list_failed_savesets or other list tools. No exclusions, no prerequisites, no mention of when an unfiltered call is appropriate.

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