ppdm-mcp-server

dd_filesystem_stats

Retrieve Data Domain filesystem capacity metrics—total, used, and available GiB plus used percentage—to check whether DD storage is running low on space.

Instructions

Get Data Domain filesystem capacity — total, used, available in GiB and used percentage. Use to check if DD is running low on space.

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

Input Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv4.2.2Nov 11, 2026

TDQS

A3.9/5.0

Behavior3/5

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

No annotations exist, so the description carries the full disclosure burden. "Get" implies a non-mutating read and the units (GiB) constrain interpretation of the numbers, but nothing is said about permissions, failure modes, or whether the figures are cached/live. For a zero-parameter read that is acceptable but not rich.

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?

Two short sentences, the resource and returned fields stated first, the usage hint second. No filler, no restating of the tool name, and nothing an agent must skip past.

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?

With no output schema, the description responsibly enumerates the returned values and their units. The one residual gap is scope granularity — whether one filesystem or a collection of filesystems is returned — which matters for a plural "filesystem capacity" reading.

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?

The tool takes zero parameters, which is the baseline-4 case; there is nothing for the description to disambiguate. The listed output metrics are a bonus rather than parameter semantics.

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?

A specific verb and resource ("Get Data Domain filesystem capacity") plus an enumeration of the exact metrics returned (total, used, available in GiB, used percentage). It is clearly a read-only capacity query rather than a configuration or listing tool, though it never names a sibling such as dd_system_info to sharpen the boundary.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

"Use to check if DD is running low on space" gives an explicit triggering condition, which is exactly the kind of guidance an agent needs. It stops short of a full when/when-not statement with a named alternative for capacity-adjacent questions like system health or storage-unit listing.

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