quickS3

Create upload URL

create_upload_url

Idempotent

Create a short-lived presigned upload URL (valid 15 minutes) for one object. Upload the file directly to your storage provider with an HTTP PUT to the returned url, sending every header in the returned headers (e.g. curl -H "x-ms-blob-type: BlockBlob" -T localfile "<url>" for Azure). Uploads fail without those headers. quickS3 never sees or stores the file contents.

Input Schema

TableJSON Schema

Name	Required	Description
`key`	Yes	Object key to write, e.g. "reports/2026/q3.csv"
`size`	Yes	File size in bytes
`bucket`	Yes	Bucket name
`overwrite`	No	Allow replacing an existing object (default false)
`contentType`	No	Content type of the file, e.g. "text/csv"
`connectionId`	Yes	Connection ID from list_connections

Output Schema

TableJSON Schema

Name	Required	Description	Default
`url`	Yes
`method`	Yes
`headers`	Yes
`maxBytes`	Yes
`expiresAt`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

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"
+    },
+    "headers": {
+      "additionalProperties": {
+        "type": "string"
+      },
+      "propertyNames": {
+        "type": "string"
+      },
+      "type": "object"
+    },
+    "maxBytes": {
+      "type": "number"
+    },
+    "method": {
+      "type": "string"
+    },
+    "url": {
+      "type": "string"
+    }
+  },
+  "required": [
+    "url",
+    "method",
+    "headers",
+    "expiresAt",
+    "maxBytes"
+  ],
+  "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?

Discloses important behavioral details beyond the annotations: the URL is valid for 15 minutes, uploads fail without the returned headers, and quickS3 never sees or stores file contents. This meaningfully informs the agent about side effects and constraints.

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?

Three focused sentences front-load the core purposehare, then add critical usage details and a concrete curl example. No filler or redundant restatement of the schema.

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?

The description, combined with the complete schema and the existence of an output schema, covers all essential aspects: URL lifetime, required headers, direct upload behavior, and the storage provider flow. An agent has enough information to invoke and complete the upload correctly.

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?

The input schema already covers all 6 parameters with descriptions, so the description does not need to elaborate. The description adds context about the returned url/headers rather than the input parameters, so baseline 3 is appropriate.

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?

States a specific verb and resource: creates a short-lived presigned upload URL scoped to one object. This clearly distinguishes it from sibling tools like create_download_link or create_share_link, which serve different purposes.

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 clear workflow context by explaining that the file should be uploaded via HTTP PUT to the returned URL, with all returned headers. It implicitly guides when to use this tool, though it does not explicitly name alternatives or state when not to use it.

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?