Skip to main content
Glama

download

DestructiveIdempotent

Copies one file from a remote workspace into the local project directory (up to 64 MiB), replacing an existing local file only when overwrite is set.

Instructions

Copy one file from the remote workspace into the LOCAL project directory (up to 64 MiB). An existing local file is only replaced with overwrite. Results show project-relative paths only.

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": {
      "remote": "<remote>"
    },
    "name": "download"
  }
}

Input Schema

NameRequiredDescriptionDefault
fleetNoFleet name. Omit to use the default.
localNoDestination in the local project directory. Default: the file name.
remoteYesFile on the remote machine.
contextNoContext name. Omit to use the default.
overwriteNoReplace an existing local file. Without it an existing file is an error.
workspaceNoWorkspace id. Omit to use this session's workspace on the fleet.

Output Schema

NameRequiredDescriptionDefault
bytesYes
localYes
whereYes
remoteYes
workspaceYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and idempotentHint=true, so the safety bar is lower. The description still adds real value: a hard 64 MiB transfer cap, the rule that an existing local file is only replaced with overwrite, and that results report project-relative paths only — none of which are in the annotations.

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?

Three short sentences, all substantive, with the operation and its scope front-loaded and the caveats (size cap, overwrite, path reporting) following in order of importance. No filler.

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 full schema coverage, complete annotations, and an output schema, the description needn't explain returns or parameter formats. It covers the operation, the size limit, overwrite semantics, and path reporting; only directory-creation behavior and partial-failure handling are left unstated.

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 100%, so the schema already explains every parameter including overwrite and local destination defaults. The description restates the overwrite behavior without adding syntax, path format, or edge-case meaning beyond the schema, so the baseline 3 applies.

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?

States a specific verb (copy) and resource (one file) plus the exact direction: remote workspace to LOCAL project directory. The explicit directionality makes it unmistakable versus a reverse-direction sibling like upload, without needing to name one.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The direction of transfer implies when to use it, but there is no explicit when-not guidance and no named alternative for the reverse operation (upload) or for files exceeding the 64 MiB cap. The agent must infer the boundary conditions from the stated limits.

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