quickS3

List storage connections

list_connections

Read-onlyIdempotent

List the storage connections (S3, R2, Spaces, B2, ...) this access grant can see, with the cached bucket inventory of each. A connection whose buckets could not be listed has bucketsError instead of buckets.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`includeBuckets`	No	Also list the cached buckets of each connection (default true). Set false to omit bucket inventories.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`connections`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

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.3/5.0

Behavior4/5

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

Annotations already declare read-only, idempotent, non-destructive behavior. The description adds valuable behavioral detail beyond annotations: results include cached bucket inventories, and a connection with failed bucket listing exposes bucketsError instead of buckets. This helps an agent anticipate error-shaped returns.

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?

Two sentences with no filler. The core action and scope are front-loaded in the first sentence, and the second sentence adds a necessary edge-case behavior (bucketsError). Every clause earns its place.

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?

For a tool with one optional, fully documented parameter, rich annotations, and an output schema, the description is complete. It covers scope, return contents, and an error variant, so an agent has everything needed to invoke the tool 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?

Schema description coverage is 100%, so the includeBuckets parameter is fully documented in the schema (default true, false omits bucket inventories). The tool description reinforces the bucket-inventory concept but does not add meaning beyond what the schema already provides, 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 ('List') and resource ('storage connections') with explicit scoping ('this access grant can see'). The examples (S3, R2, Spaces, B2) and mention of cached bucket inventory make it clearly distinct from sibling tools 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 Guidelines4/5

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

The description provides clear context: this tool enumerates connections visible to an access grant and includes their bucket inventories. It does not explicitly state when to choose this over list_buckets or list_objects, but the resource-level distinction is clear enough that an agent can infer the appropriate use.

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?