Skip to main content
Glama

upload_file

Upload a local file to a GPU runtime's contents root using a relative remote path, so training scripts and datasets are available for remote runs.

Instructions

Upload a local file to the runtime (path is relative to the runtime's contents root).

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

Input Schema

NameRequiredDescriptionDefault
local_pathYes
remote_pathYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

B3.2/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full behavioral burden, and it does add one substantive fact: remote paths resolve against the runtime's contents root. It remains silent on overwrite behavior when remote_path already exists, size or rate limits, and permission/auth requirements, which are the main risks for an upload.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single front-loaded sentence with no filler and no repetition of the tool name. It is efficient, though the brevity edges toward under-specification rather than crispness.

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?

An output schema exists, so return values need not be described. For a two-parameter file-transfer tool with no annotations, though, the definition should still cover the runtime-connected prerequisite, local_path semantics, and overwrite behavior; two of those three gaps are unaddressed.

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 description coverage is 0%, so the two required parameters are otherwise undefined. The parenthetical clarifies how remote_path is interpreted (relative to the contents root), which is real added meaning, but local_path gets no guidance at all (absolute vs relative, file vs directory), so compensation is only partial.

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 uses a specific verb and resource ('Upload a local file to the runtime') and implicitly routes away from download_file by stating the direction of transfer. It does not name any sibling explicitly, so it stops short of full disambiguation against the many other upload/runtime tools.

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 statement of when to use this rather than download_file, hf_upload, or the various runtime_start/connect tools, and no prerequisites are given. The phrase 'the runtime' hints that a connected runtime is required but never says so, leaving the agent to infer the setup step.

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