Skip to main content
Glama
alebgl77

ftp-deploy-mcp

by alebgl77
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Remote

Upload a local file

ftp_upload
Destructive

Upload a local file to an FTP/FTPS/SFTP server, auto-creating missing parent directories. Set a remote path or default to the file name at the server root.

Instructions

Upload one local file to the server, auto-creating parent directories. Remote path defaults to the file basename at the root.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
serverNoName of the configured server. Defaults to the configured default, or the sole server.
local_pathYesLocal file path, absolute or relative to the server's configured localRoot.
remote_pathNoDestination remote path, relative to the server root. Defaults to the local basename at the root.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.2.0
    • changedInput schema / properties / local_path / description
      Previous value: -"Local file path (relative paths resolve against the process cwd)."New value: +"Local file path, absolute or relative to the server's configured localRoot."
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "oneOf": [
+    {
+      "additionalProperties": false,
+      "properties": {
+        "local_path": {
+          "type": "string"
+        },
+        "remote_path": {
+          "type": "string"
+        },
+        "security_warning": {
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "server": {
+          "type": "string"
+        },
+        "size_bytes": {
+          "minimum": 0,
+          "type": "number"
+        }
+      },
+      "required": [
+        "server",
+        "local_path",
+        "remote_path",
+        "size_bytes",
+        "security_warning"
+      ],
+      "type": "object"
+    },
+    {
+      "additionalProperties": false,
+      "properties": {
+        "error": {
+          "additionalProperties": false,
+          "properties": {
+            "code": {
+              "enum": [
+                "CONFIG_REQUIRED",
+                "CONFIG_INVALID",
+                "SERVER_REQUIRED",
+                "SERVER_UNKNOWN",
+                "INVALID_ARGUMENT",
+                "READ_ONLY",
+                "TRANSPORT_POLICY",
+                "HOST_KEY_REJECTED",
+                "REMOTE_ROOT_REJECTED",
+                "PATH_REJECTED",
+                "NOT_FOUND",
+                "ALREADY_EXISTS",
+                "TRANSFER_LIMIT",
+                "TRANSFER_VERIFY",
+                "TARGET_CHANGED",
+                "CANCELLED",
+                "TIMEOUT",
+                "DEPLOY_PARTIAL",
+                "TRANSPORT_ERROR",
+                "OUTPUT_LIMIT",
+                "INTERNAL_ERROR",
+                "SCAN_LIMIT",
+                "CAPACITY_LIMIT"
+              ],
+              "type": "string"
+            },
+            "effects": {
+              "enum": [
+                "none",
+                "possible",
+                "confirmed"
+              ],
+              "type": "string"
+            },
+            "message": {
+              "type": "string"
+            },
+            "next_action": {
+              "enum": [
+                "fix_input",
+                "fix_config",
+                "select_server",
+                "inspect_target",
+                "retry",
+                "contact_operator",
+                "none"
+              ],
+              "type": "string"
+            },
+            "partial": {
+              "additionalProperties": false,
+              "properties": {
+                "completed_bytes": {
+                  "maximum": 9007199254740991,
+                  "minimum": 0,
+                  "type": "integer"
+                },
+                "completed_files": {
+                  "maximum": 9007199254740991,
+                  "minimum": 0,
+                  "type": "integer"
+                },
+                "failed_files": {
+                  "maximum": 9007199254740991,
+                  "minimum": 0,
+                  "type": "integer"
+                },
+                "final": {
+                  "type": "boolean"
+                },
+                "total_files": {
+                  "maximum": 9007199254740991,
+                  "minimum": 0,
+                  "type": "integer"
+                }
+              },
+              "required": [
+                "completed_files",
+                "completed_bytes",
+                "failed_files",
+                "final"
+              ],
+              "type": "object"
+            },
+            "request_id": {
+              "format": "uuid",
+              "type": "string"
+            },
+            "retryable": {
+              "type": "boolean"
+            },
+            "schema_version": {
+              "const": 1,
+              "type": "number"
+            }
+          },
+          "required": [
+            "schema_version",
+            "code",
+            "message",
+            "retryable",
+            "request_id",
+            "next_action",
+            "effects"
+          ],
+          "type": "object"
+        }
+      },
+      "required": [
+        "error"
+      ],
+      "type": "object"
+    }
+  ],
+  "type": "object"
+}
  2. First observedv0.1.0

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and readOnlyHint=false, which signal a mutating operation. The description adds the auto-creation of parent directories and the default remote path behavior, which are valuable non-obvious details. It does not disclose potential overwrites of existing files, but the annotation covers the destructive aspect, so the description adds appropriate context.

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 description is one tight sentence with no filler. The key behavioral details are front-loaded: action, auto-creation, and default path. Every word contributes, and it is neither under-specified nor verbose.

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 an output schema present to document return values and annotations covering safety, the description is complete enough. It covers the primary behavior and defaults. It may not cover edge cases like what happens if the file doesn't exist, but given the context, it is adequately comprehensive for an upload tool.

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 description coverage is 100%, so the schema documents each parameter clearly. The description adds the default remote path behavior (basename at root) and clarifies the auto-creation of directories, which complements the schema. This is more than a simple restatement, adding value over the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the action: uploading a single local file to the server, with the specific behavior of auto-creating parent directories. It distinguishes itself from siblings like ftp_deploy (which likely uploads multiple files or directories) and ftp_download, and the default remote path behavior is clearly explained.

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?

The description clearly implies use for single-file uploads and implicitly contrasts with ftp_deploy for bulk deployments, but it does not explicitly state when to use this versus alternatives. It provides no explicit exclusions, but the context is enough for an agent to infer the intended use.

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