Skip to main content
Glama

upload_file

Uploads a local file to a new relative path in a remote Blender workspace, avoiding overwrites so existing project files remain intact.

Instructions

Upload a local file to a new relative workspace path. Never overwrites.

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>",
      "local_path": "<local_path>",
      "remote_path": "<remote_path>"
    },
    "name": "upload_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.9/5.0
Behavior3/5

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

With no annotations, the description carries the full burden, and it does disclose one important trait: 'Never overwrites.' However, it does not say what actually happens on collision (error, abort, or failure response), whether the upload is atomic, what permissions are required, or what the tool returns, leaving meaningful behavioral gaps for a mutation/transfer operation.

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 short sentences, zero waste, with the destination scope front-loaded and the safety constraint second. The phrasing 'new relative workspace path' is slightly compressed and could be clearer, but nothing is redundant.

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?

For a 3-parameter tool with no annotations, no output schema, and 0% schema coverage, the description is too thin. Key caller needs — path format conventions, the role of session_id, collision behavior, and expected result — are absent.

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%, so the description must compensate, and it largely does not. It implies the meaning of local_path and remote_path only obliquely, gives no format for the relative path, and never mentions session_id at all, leaving one of three required parameters entirely unexplained.

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 states a specific verb and resource ('Upload a local file') plus the destination scope ('a new relative workspace path'). It is clearly the inverse of the sibling download_file, though it never names that sibling or any other alternative explicitly.

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 guidance on when to use this versus alternatives such as save_project or list_files, nor any prerequisites. The only usable inference is that the target path must be a 'new' path, which hints at the failure case but is presented as behavior rather than usage instruction.

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