Skip to main content
Glama

download_file

Retrieve a file from a remote Blender workspace and save it to a new local filename, with support for transfers up to 5 GB.

Instructions

Download a workspace file to a new local filename. Maximum size 5 GB.

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

Input Schema

NameRequiredDescriptionDefault
local_pathYes
session_idYes
remote_pathYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.7/5.0
Behavior2/5

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

With no annotations present, the description carries the entire behavioral burden, and it discloses only one trait: a 5 GB maximum file size. It says nothing about whether an existing local file is overwritten (a real risk given "new local filename"), whether the call blocks until completion, required permissions, or behavior on failure/partial transfer.

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?

Two compact sentences with the action front-loaded and the size limit placed as a secondary constraint; nothing is wasted. The brevity borders on under-specification, but there is no filler to trim.

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

Completeness2/5

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

There is no output schema and no annotations, so the description is the only source of behavioral and parameter information, yet it omits session semantics, overwrite behavior, and any notion of the return value. For a three-required-parameter, undocumented-schema tool, this is too thin to call complete.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% and all three parameters are required, so the description must compensate. It only loosely maps "workspace file" to remote_path and "new local filename" to local_path, and never mentions session_id at all, leaving the most obscure required parameter entirely undefined.

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?

"Download a workspace file to a new local filename" pairs a specific verb (download) with a specific resource (workspace file) and states the transfer direction, which implicitly separates it from the upload_file sibling. It stops short of naming any sibling or exclusion explicitly, so it is clear but not fully differentiated.

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 guidance on when to choose this tool versus list_files (to discover a path first) or upload_file, and no stated prerequisites such as needing an active session. The only usable constraint is the 5 GB ceiling, which is a limit rather than usage guidance.

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