quickS3

Create download link

create_download_link

Read-onlyIdempotent

Create a short-lived download link (valid 5 minutes, single use) for one object. Download the file by following the link, e.g. with curl -L -o output.bin "<uri>". quickS3 never sees or stores the file contents; the link redirects directly to your storage provider.

Input Schema

TableJSON Schema

Name	Required	Description
`key`	Yes	Object key, e.g. "reports/2026/q3.csv"
`bucket`	Yes	Bucket name
`connectionId`	Yes	Connection ID from list_connections

Output Schema

TableJSON Schema

Name	Required	Description	Default
`url`	Yes
`expiresAt`	Yes
`transferId`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedSep 17, 2026

addedOutput schema / properties / url
```
Added value: +{
+  "type": "string"
+}
```

changedOutput schema / required

Previous value: -[
-  "transferId",
-  "expiresAt"
-]New value: +[
+  "url",
+  "transferId",
+  "expiresAt"
+]

Changed1 schema field changedSep 16, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "https://json-schema.org/draft/2020-12/schema",
+  "additionalProperties": false,
+  "properties": {
+    "expiresAt": {
+      "type": "string"
+    },
+    "transferId": {
+      "type": "string"
+    }
+  },
+  "required": [
+    "transferId",
+    "expiresAt"
+  ],
+  "type": "object"
+}

First observedSep 16, 2026

TDQS

A4.5/5.0

Behavior5/5

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

Beyond annotations, the description discloses valuable behavioral details: the link is valid for 5 minutes, single use, redirects directly to the storage provider, and quickS3 never sees or stores file contents. This meaningfully enriches the readOnly and non-destructive hints already present.

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 compact and well-structured: it states the core behavior first, then usage via curl, then a useful privacy guarantee. Every sentence contributes meaningful information without redundancy.

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?

Given the simple 3-parameter schema, 100% schema coverage, an output schema, and annotations covering safety, the description provides all necessary operational context. An agent has enough information to call the tool correctly and understand the resulting link's behavior.

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 description coverage is 100%, so the schema already documents connectionId, bucket, and key with examples. The description adds general context about the generated link but does not add further parameter-level detail, matching the baseline for high schema coverage.

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 clearly states a specific verb and resource: 'Create a short-lived download link ... for one object.' It also distinguishes itself from siblings like create_upload_url and create_share_link by emphasizing download, short validity, and single-use behavior.

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 gives clear context on when this tool is appropriate: for downloading one specific object via a short-lived, single-use link. It does not explicitly name alternatives or exclusions, but the download vs upload/link-sharing distinction is clear enough for an agent to route correctly.

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

All quickS3 tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?