quickS3

List storage connections

list_connections

Read-onlyIdempotent

List the storage connections (S3, R2, Spaces, B2, and others) that this access grant can see. Each connection includes its cached list of buckets. If the buckets of a connection could not be listed, that connection has bucketsError instead of buckets.

Input Schema

Name	Required	Description	Default
`includeBuckets`	No	Include the cached list of buckets for each connection (default true). Set to false to leave the buckets out.

Output Schema

Name	Required	Description	Default
`connections`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 21, 2026

changedInput schema / properties / includeBuckets / description

Previous value: -"Also list the cached buckets of each connection (default true). Set false to omit bucket inventories."New value: +"Include the cached list of buckets for each connection (default true). Set to false to leave the buckets out."

Changed3 schema fields changedSep 21, 2026

changedInput schema / properties / includeBuckets / description

Previous value: -"Also list the buckets of each connection (default true). Set false for a faster answer without contacting the storage providers."New value: +"Also list the cached buckets of each connection (default true). Set false to omit bucket inventories."

addedOutput schema / properties / connections / items / properties / bucketsRefreshedAt
```
Added value: +{
+  "type": "string"
+}
```
addedOutput schema / properties / connections / items / properties / bucketsStale
```
Added value: +{
+  "type": "boolean"
+}
```

Changed3 schema fields changedSep 17, 2026

addedInput schema / properties / includeBuckets

Added value: +{
+  "description": "Also list the buckets of each connection (default true). Set false for a faster answer without contacting the storage providers.",
+  "type": "boolean"
+}

addedOutput schema / properties / connections / items / properties / buckets

Added value: +{
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}

addedOutput schema / properties / connections / items / properties / bucketsError
```
Added value: +{
+  "type": "string"
+}
```

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": {
+    "connections": {
+      "items": {
+        "additionalProperties": false,
+        "properties": {
+          "canRead": {
+            "type": "boolean"
+          },
+          "canWrite": {
+            "type": "boolean"
+          },
+          "id": {
+            "type": "string"
+          },
+          "name": {
+            "type": "string"
+          },
+          "provider": {
+            "type": "string"
+          }
+        },
+        "required": [
+          "id",
+          "name",
+          "provider",
+          "canRead",
+          "canWrite"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    }
+  },
+  "required": [
+    "connections"
+  ],
+  "type": "object"
+}

First observedSep 16, 2026

TDQS

A4/5.0

Behavior4/5

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

Annotations already cover read-only, idempotent, and open-world traits, so the bar is lower; the description still adds real value by explaining that each connection carries a cached bucket list and that failed listings surface as a bucketsError field instead of buckets.

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 tight sentences with zero filler; the core purpose is front-loaded and the two follow-on sentences each add distinct return-shape detail.

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?

With an output schema present, return values needn't be explained, and the description adequately covers scope plus the bucketsError edge case. It could note the includeBuckets toggle to be fully self-contained, but nothing essential for correct invocation is missing.

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% and the single includeBuckets parameter is fully documented in the schema. The description never mentions the parameter, so it adds no semantic value beyond what the schema provides – baseline 3.

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 ('List the storage connections'), enumerates the concrete providers (S3, R2, Spaces, B2), and scopes it to 'this access grant can see'. This distinguishes it clearly from siblings like list_buckets and list_objects.

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

Usage Guidelines3/5

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

The grant-scoping phrase implies context, but there is no explicit when-to-use or when-not-to-use guidance, and no alternative tool is named (e.g., list_buckets for drilling into a single connection's buckets). Usage must be inferred.

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?