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

ppdm-mcp-server

by Moodswing9
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

list_restore_sessions

List PPDM restore sessions and filter by state (RUNNING, COMPLETED, FAILED), or leave blank to view all recent restore sessions.

Instructions

List PPDM restore sessions — filter by state (RUNNING, COMPLETED, FAILED) or leave blank for all recent sessions

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": "list_restore_sessions"
  }
}

Input Schema

NameRequiredDescriptionDefault
filterNoOData filter, e.g. state eq "RUNNING"

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv4.2.2

TDQS

A3.7/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full burden. 'List' implies a read-only operation and the blank-filter default is useful behavioral context, but it does not mention pagination, permissions, or return shape.

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?

The definition is a single front-loaded sentence with no filler. Every clause contributes scope or parameter meaning.

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 simple one-parameter list tool with no output schema, the description covers the resource, filter values, and default behavior. It could say more about return ordering or pagination, but nothing critical is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, but the description adds value beyond the generic OData filter example by naming the allowed state values RUNNING, COMPLETED, and FAILED and stating that a blank filter returns all recent sessions.

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: 'List PPDM restore sessions'. The scope is clear, and it implicitly differs from status-fetching siblings like get_restore_status, though it does not explicitly name those alternatives.

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?

Gives implied usage by saying to filter by state or leave blank for all recent sessions. It does not explicitly say when to use this instead of get_restore_status or list_failed_jobs, so the agent must infer the distinction.

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