Skip to main content
Glama

upload

Upload a file or folder from your computer to a remote host over SFTP, replacing any existing file at the destination path.

Instructions

Upload a file or folder from this computer to a host. An existing file there is replaced.

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": {
      "host": "<host>",
      "remote_path": "<remote_path>",
      "local_path": "<local_path>"
    },
    "name": "upload"
  }
}

Input Schema

NameRequiredDescriptionDefault
hostYes
local_pathYesThe path on this computer.
remote_pathYesThe path on the host.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.3/5.0
Behavior3/5

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

With no annotations supplied, the description carries the full behavioral burden, and it does disclose one critical trait: an existing file at the destination is replaced. That is genuinely valuable. However, it says nothing about whether folder uploads recurse, permission or auth requirements, overwrite confirmation, or what is returned on success or failure.

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, zero filler, and the destructive overwrite behavior is surfaced immediately rather than buried. Nothing could be removed without losing information.

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

Completeness3/5

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

For a three-required-parameter mutation tool with no annotations and no output schema, the definition covers purpose and the key destructive side effect but leaves gaps around recursion for folders, host identifier format, and result reporting. Adequate but not complete.

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?

Schema coverage is 67% and both path parameters already carry short definitions. The description adds the useful framing that local_path is 'this computer' and remote_path is 'the host', but 'host' itself remains undocumented in both schema and description (is it a name from list_hosts or an address?).

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 (upload) and resource (file or folder) plus the direction of transfer (from this computer to a host), which distinguishes it from the reverse-direction 'download' sibling. It stops short of naming any sibling explicitly, so differentiation relies on the agent inferring direction.

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?

There is no explicit when-to-use or when-not-to-use guidance. The agent must infer from 'from this computer to a host' that this is the counterpart to download and distinct from sync_now, and no preconditions (session open, host added, access granted) are mentioned.

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