Skip to main content
Glama

Vee3

by io.github.Vee3io

files.upload_file

Reserve a direct upload slot for a local file or folder.

Pass the desired file_name. For a single file, this becomes the stored name. For a folder, this becomes the destination folder prefix. To nest further, use a path in file_name (folder/subfolder/.../name). Optionally pass retention_days (default 7, minimum 1). The name may omit an extension. Vee3 returns an upload_code.

Install the Vee3 CLI once with npm install -g @vee3/cli (requires Node 18+), then run vee3-upload {upload_code} {file_or_folder_path} in the terminal. The CLI accepts a file or a folder. A folder uploads every nested file in one command and stores each file under the reserved file_name prefix, preserving relative paths. The CLI resolves the code to signed upload URLs, streams the local file or files to Vee3 storage, and prints each stored file_name after the upload finishes. Use those file_name values in files.list_uploaded_files and other capabilities. The CLI does not need an API key. When a stored file already uses the same name, the upload stops, skips that file, or replaces it.

If installation fails with a TLS or certificate error (common on networks that inspect HTTPS traffic), use Node 22.15 or newer and run with NODE_OPTIONS=--use-system-ca, or configure npm to trust your network's root certificate.

Each file can be up to 2 GB. One folder upload can include up to 500 files. Retention is chosen at reserve time (default 7 days) and applies to every file in the folder. After each upload is detected, Vee3 bills max(1, ceil(size_gibibytes * retention_days * 2)) tokens per file. Upload codes can be resolved within 60 minutes of reserve.

Use files.list_uploaded_files to list stored uploads for follow-up work.

Cost = 0 tokens to reserve. After upload completes, billing is max(1, ceil(size_gibibytes * retention_days * 2)) tokens.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
file_nameYesDesired file name or path for the uploaded file. Use folder/subfolder/.../file_name to organize files in folders. Extension is optional and is replaced based on detected file type. Do not use '..' or absolute paths.
existing_filesNoWhat to do when a stored file already uses the same name. 'stop' (default) fails on the first duplicate. 'continue' skips duplicates and keeps uploading remaining files. 'replace' overwrites duplicated stored files.stop
retention_daysNoHow many days to keep the file after upload completes. Default 7. Billing uses size and this retention.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
commandNoSuggested terminal command for uploading the local file or folder.
max_bytesNoMaximum allowed file size in bytes.
upload_idNoStable identifier for the reserved upload.
expires_atNoISO 8601 timestamp when the upload code can no longer be resolved (60 minutes after reserve).
upload_codeNoShort code to pass to the @vee3/upload CLI.
existing_filesNoPolicy for files that already exist: stop, continue, or replace.
retention_daysNoDays the file will be retained after upload completes.
install_commandNoOne-time command to install the Vee3 CLI (`npm install -g @vee3/cli`). On networks that inspect HTTPS, install may require Node 22.15+ with NODE_OPTIONS=--use-system-ca.
troubleshootingNoWhat to do if installation or uploading fails: re-read this tool's description via meta-tools.describe for setup and troubleshooting steps.

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed3 schema fields changed
    • addedInput schema / properties / existing_files
      Added value: +{
+  "anyOf": [
+    {
+      "enum": [
+        "stop",
+        "continue",
+        "replace"
+      ],
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": "stop",
+  "description": "What to do when a stored file already uses the same name. 'stop' (default) fails on the first duplicate. 'continue' skips duplicates and keeps uploading remaining files. 'replace' overwrites duplicated stored files.",
+  "title": "Existing Files"
+}
    • changedOutput schema / properties / command / description
      Previous value: -"Suggested terminal command for uploading the local file."New value: +"Suggested terminal command for uploading the local file or folder."
    • addedOutput schema / properties / existing_files
      Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Policy for files that already exist: stop, continue, or replace.",
+  "title": "Existing Files"
+}
  2. Added

TDQS

A4.7/5.0
Behavior5/5

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

With no annotations, the description carries the disclosure burden and succeeds: it reveals the reserve-then-CLI flow, 60-minute code expiry, duplicate-handling behavior, 2 GB/500-file limits, retention default, and exact token-billing formula. This is far beyond what the tool name or schema alone would tell an agent.

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?

Front-loaded core purpose and organized into logical paragraphs covering workflow, prerequisites, limits, and billing. It is long, and the billing formula plus files.list_uploaded_files guidance are each mentioned twice, so a little trimming/repetition remains.

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

Completeness5/5

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

For a tool that spans an API reservation plus an external CLI upload, the description covers prerequisites, installation, error handling for TLS failures, operational limits, expiry, billing, and follow-up listing. With an output schema present, no return-value detail is missing, and no important call-time decision is left unexplained.

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

Parameters5/5

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

Schema coverage is 100%, so the baseline is 3, but the description adds substantial meaning: file_name doubles as single stored name or folder prefix, supports nesting and extension omission; retention_days default/minimum and billing interaction are explained; existing_files behavior is described in plain language. This meaningfully exceeds the schema fields.

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?

First sentence names a specific action and resource: 'Reserve a direct upload slot for a local file or folder.' It then clarifies the non-obvious behavior—this tool returns an upload_code and the actual transfer happens via the Vee3 CLI—so an agent won't mistake it for an immediate upload, and the flow is distinguishable from files.download_file/delete_file/list_uploaded_files.

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

Usage Guidelines4/5

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

Provides extensive usage context: pass file_name, choose retention_days, install/run the CLI on the local machine, and use files.list_uploaded_files for follow-up. It does not explicitly enumerate when-not-to-use scenarios or name sibling alternatives for upload (none exist), so it falls just short of an explicit alternative-selection rule.

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

All Vee3 toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.1/5.0
Disambiguation5/5

Each tool has a distinct purpose, further clarified by group prefixes and clear descriptions. Within each group, tools perform different operations (e.g., domains.lookup vs. domains.whois vs. domains.rdap) with no ambiguity.

Naming Consistency5/5

All tools follow a consistent group.tool_name pattern using snake_case. The naming is predictable and uniformly applied across all groups.

Tool Count4/5

78 tools is high, but the server aggregates multiple distinct API domains (11 groups). Each group has a reasonable number of tools, typically under 10, with TikTok having 17. The count reflects breadth, not bloat.

Completeness5/5

Each domain's tool set covers the primary expected operations (e.g., search, details, reviews, metrics, user info). There are no obvious gaps for read-only analytical use; features like posting are likely out of scope.

Resources