Skip to main content
Glama
Sign In
sftp-mcp

sftp-mcp

by Guipegoraro
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

sftp_enviar

Destructive

Upload a local file to an SFTP server, placing it in the target remote directory or path. If the destination exists, set overwrite=true to back up the current version before replacement.

Instructions

Envia um arquivo local ao servidor. caminho_remoto terminado em "/" ou que seja pasta recebe o nome do arquivo local. Respeita raizes_escrita, se o perfil tiver. Se o destino existe, exige sobrescrever=true e baixa a versao atual para backups/ antes de substituir.

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": {
      "perfil": "<perfil>",
      "arquivo_local": "<arquivo_local>",
      "caminho_remoto": "<caminho_remoto>"
    },
    "name": "sftp_enviar"
  }
}

Input Schema

NameRequiredDescriptionDefault
perfilYes
sobrescreverNo
arquivo_localYes
caminho_remotoYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.6/5.0
Behavior5/5

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

Beyond the annotations, the description discloses the critical overwrite guard and backup behavior: if the destination exists, sobrescrever=true is required and the current version is moved to backups/ before replacement. It also mentions write-root enforcement from the profile, which is important behavioral context for a destructive upload tool.

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 three dense sentences with no wasted wording. It front-loads the core action, then follows with path semantics, write-root constraints, and overwrite/backup behavior.

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 destructive remote-write tool with four required parameters and no output schema, the description covers the main invocation risks: destination path handling, overwrite gating, and backups. The main gap is that the required 'perfil' parameter is not fully explained, though its role is partially implied.

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?

With 0% schema description coverage, the description compensates well by explaining caminho_remoto's folder-ending behavior, sobrescrever's role, and the local-file-to-remote-name mapping. It still leaves 'perfil' only implicitly explained through the write-roots mention, and does not specify local path format, so it is strong but not complete.

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 states a specific verb and resource: 'Envia um arquivo local ao servidor', making the upload direction explicit. Among the sftp_* siblings, this clearly reads as the upload/write tool rather than a read, list, download, or search operation.

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?

It gives clear usage conditions: remote paths ending in '/' or pointing to a folder receive the local filename, write roots are respected, and overwriting requires sobrescrever=true. It does not explicitly compare against sibling tools or say when not to use this tool, but the operational context is clear.

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