Skip to main content
Glama
webapper-services

CloudSee Drive MCP Server

by webapper-services
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Restore archived file

restore_archived_file
Destructive

Restore an archived S3 Glacier object for download by specifying its key, storage ID, and retrieval days. Confirm to initiate retrieval, which may take minutes to hours.

Instructions

Begin restoring an archived (S3 Glacier) object so it can be downloaded. Requires the drive (bucketName). This is Glacier un-archiving — NOT recovery of a deleted file — and may incur retrieval cost and take minutes to hours. Requires confirm=true. (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
daysYesHow many days to keep the restored copy available.
confirmNoMust be true to actually perform this mutating/irreversible action. If omitted or false, the tool returns a preview and makes no changes.
objectKeyYesObject key of the archived (Glacier) object to restore.
storageIdYesStorage/index id of the object — the StorageId field returned by search_files, browse_folder, or get_file_metadata. NOTE: the ids from list_files and recent_files belong to a different id space and will NOT work here.
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.
retrievalTierNoGlacier retrieval tier (default Standard).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv3.1.4
    • changedInput schema / properties / storageId / description
      Previous value: -"Optional storage/index id."New value: +"Storage/index id of the object — the StorageId field returned by search_files, browse_folder, or get_file_metadata. NOTE: the ids from list_files and recent_files belong to a different id space and will NOT work here."
    • addedInput schema / properties / storageId / minLength
      Added value: +1
    • changedInput schema / required
      Previous value: -[
-  "objectKey"
-]New value: +[
+  "objectKey",
+  "days",
+  "storageId"
+]
  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?

Annotations already mark this as destructive/non-readonly, but the description adds substantial context: retrieval cost, long completion time, required confirmation, and RBAC denial semantics. It also clarifies this is Glacier un-archiving, not deletion recovery. No contradiction with 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?

The description is front-loaded with the core purpose, and each subsequent sentence adds a distinct operational fact. Parentheticals keep the caveats compact without bloating the main message.

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?

The description covers safety, cost, latency, confirmation requirements, authorization semantics, and the deleted-file distinction. It could be slightly more explicit about what the caller should expect in response, but the async 'begin restoring' behavior and confirm-preview semantics in the schema make it sufficiently complete.

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 coverage is 100% and parameter descriptions are already detailed, including the storageId id-space warning and confirm preview behavior. The description adds no additional parameter-level meaning beyond what the schema provides, 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?

The description states a specific operation ('Begin restoring an archived (S3 Glacier) object so it can be downloaded') and clearly distinguishes it from recovering a deleted file. It is easy to tell apart from sibling tools like download_file or delete_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?

The description states key prerequisites (bucketName, confirm=true) and caveats (retrieval cost, minutes-to-hours latency). It explicitly says this is NOT deleted-file recovery, giving an exclusion, though it does not name an alternative tool for that case.

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