ftp-mcp

ftp_dir_size

Calculate the total size of a remote directory recursively, including all subdirectories and files, to assess storage usage across FTP/FTPS/SFTP connections.

Instructions

Calculate the total size of a remote directory recursively

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": {
      "connection": "<connection>",
      "path": "<path>"
    },
    "name": "ftp_dir_size"
  }
}

Input Schema

Name	Required	Description	Default
`path`	Yes	Remote directory path
`connection`	Yes	Connection name

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Aug 9, 2026

TDQS

C2.9/5.0

Behavior2/5

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

No annotations are provided, and the description only states the core operation. It does not disclose potential cost of recursive scans, behavior on missing paths, or whether an existing connection is required, leaving important behavioral context undocumented.

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?

A single sentence with no filler, directly and efficiently stating the tool's function. It is front-loaded and every word earns its place.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema and no annotations, the description omits return format (e.g., bytes vs human-readable) and prerequisites (e.g., requires an existing connection). While the core purpose is clear, operational details are left ambiguous, making it less complete for agent invocation.

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 input schema already provides clear descriptions for both parameters (path as remote directory, connection as connection name) with 100% coverage. The description adds the recursive behavior but no new parameter-level insights, so the baseline of 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?

The description clearly states the tool calculates the total size of a remote directory recursively, providing a specific verb and resource. It distinguishes from siblings like ftp_stat by focusing on recursive directory size, though it does not explicitly name alternatives.

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?

No guidance is provided on when to use this tool versus alternatives such as ftp_stat or ftp_tree. The recursive scope implies whole-directory sizing, but there is no explicit when/when-not or alternative recommendation.

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