Skip to main content
Glama
webapper-services

CloudSee Drive MCP Server

by webapper-services
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Upload file

upload_file

Upload a file from your machine into a CloudSee drive folder; large files are split automatically and existing names get a timestamp to prevent overwrites.

Instructions

Upload a file into a folder of a drive. The file is read from the machine running this server — which, over this connection, is your own machine — so pass its path. Requires the drive (bucketName). Files up to 8 MiB are sent in one piece; larger ones are split into parts automatically. If the name is already taken, a timestamped name is used instead, so an existing file is never overwritten. Indexing is asynchronous, so a file that uploaded successfully is still absent from browse_folder / search_files / list_files for a while afterwards — keep listing until it appears instead of uploading it again. (Write access is authorized server-side by the public API's RBAC — a denial means the API key lacks this tool's scope, not a tool failure.)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
fileNameNoName to store the file as. Defaults to the local file's name.
localPathYesPath to the file to upload, on the machine running this server. Copy the name exactly — invisible characters in a file name are a common cause of 'not found'.
bucketNameNoThe CloudSee drive (S3 bucket) name to operate in, e.g. 'max-2778abc0' — find it in the CloudSee dashboard. Required unless CLOUDSEE_DEFAULT_BUCKET is configured on the server.
storageClassNoOptional S3 storage class (e.g. STANDARD, INTELLIGENT_TIERING).
destinationFolderNoDestination folder/prefix in the drive. Omit or empty = drive root.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv2.0.2
    • removedInput schema / properties / contentType
      Removed value: -{
-  "description": "MIME type. Defaults to application/octet-stream.",
-  "type": "string"
-}
    • changedInput schema / properties / destinationFolder / description
      Previous value: -"Destination folder/prefix in the drive. Empty = drive root."New value: +"Destination folder/prefix in the drive. Omit or empty = drive root."
    • changedInput schema / properties / localPath / description
      Previous value: -"Path to the local file to upload (absolute, or relative to the server's working directory)."New value: +"Path to the file to upload, on the machine running this server. Copy the name exactly — invisible characters in a file name are a common cause of 'not found'."
    • changedInput schema / required
      Previous value: -[
-  "localPath",
-  "destinationFolder"
-]New value: +[
+  "localPath"
+]
  2. First observedv1.0.0

TDQS

A4.4/5.0
Behavior5/5

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

Beyond annotations, the description discloses several non-obvious behaviors: the file is read from the local machine, files over 8 MiB are split automatically, existing files are never overwritten, indexing is asynchronous, and RBAC denials indicate a scope issue rather than a tool failure. This is exactly the behavioral context an agent needs.

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?

The description is front-loaded with the core purpose and each subsequent sentence covers a distinct, operationally relevant behavior. It is dense but every clause earns its place, including the parenthetical RBAC clarification.

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?

It covers the local-path requirement, bucket requirement, size handling, collision behavior, async indexing, and auth errors—most of what an agent needs to invoke this correctly. The only notable gap is the absence of an explicit statement about the tool's return value or confirmation of success, and no output schema is provided to fill that gap.

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?

Input schema coverage is 100%, so the schema already documents all five parameters. The description adds useful context for localPath and bucketName and explains collision behavior related to fileName, but it does not add meaning beyond the schema for storageClass or destinationFolder.

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?

The description opens with a specific action and resource: 'Upload a file into a folder of a drive.' This is unambiguous and clearly distinguishes it from siblings such as download_file, move_file, and create_folder.

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?

The description makes the intended use clear: upload a local file into a drive folder when you have its path. It also gives strong operational guidance, such as verifying with browse_folder/search_files/list_files instead of re-uploading while indexing lags, but it does not explicitly contrast this tool with alternative creation or upload tools.

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

Deploy Server

Other Tools