IronShard Object Storage Sandbox

Get Bucket

get_bucket

Read-onlyIdempotent

Return bucket details with storage and egress usage.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`bucket_name`	Yes	Bucket to operate on.
`bucket_token`	Yes	Secret bearer token returned with the public bucket.

Output Schema

TableJSON Schema

Name	Required	Description
`egress`	Yes	Monthly egress quota and current UTC-calendar-month usage in bytes.
`storage`	Yes	Storage quota and current usage in bytes.
`created_at`	Yes	UTC creation time
`bucket_name`	Yes	Bucket to operate on.
`object_count`	Yes	Number of objects
`versioning_enabled`	Yes	Whether object versioning is enabled.

Schema Changelog

Changes observed during successful MCP inspections.

Changed15 schema fields changedSep 3, 2026

removedOutput schema / properties / created_at / anyOf

Removed value: -[
-  {
-    "format": "date-time",
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]

removedOutput schema / properties / created_at / default
```
Removed value: -null
```

changedOutput schema / properties / created_at / description

Previous value: -"UTC creation time, when available."New value: +"UTC creation time"

addedOutput schema / properties / created_at / format
```
Added value: +"date-time"
```
addedOutput schema / properties / created_at / type
```
Added value: +"string"
```

removedOutput schema / properties / object_count / anyOf

Removed value: -[
-  {
-    "minimum": 0,
-    "type": "integer"
-  },
-  {
-    "type": "null"
-  }
-]

removedOutput schema / properties / object_count / default
```
Removed value: -null
```

changedOutput schema / properties / object_count / description

Previous value: -"Number of objects, when requested and available."New value: +"Number of objects"

addedOutput schema / properties / object_count / minimum
```
Added value: +0
```
addedOutput schema / properties / object_count / type
```
Added value: +"integer"
```

removedOutput schema / properties / versioning_enabled / anyOf

Removed value: -[
-  {
-    "type": "boolean"
-  },
-  {
-    "type": "null"
-  }
-]

removedOutput schema / properties / versioning_enabled / default
```
Removed value: -null
```

changedOutput schema / properties / versioning_enabled / description

Previous value: -"Whether object versioning is enabled, when available."New value: +"Whether object versioning is enabled."

addedOutput schema / properties / versioning_enabled / type
```
Added value: +"boolean"
```

changedOutput schema / required

Previous value: -[
-  "bucket_name",
-  "storage",
-  "egress"
-]New value: +[
+  "bucket_name",
+  "created_at",
+  "object_count",
+  "versioning_enabled",
+  "storage",
+  "egress"
+]

First observedSep 1, 2026

TDQS

A4.1/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the description does not need to restate safety. It adds a small amount of behavioral context by naming the specific usage fields returned, but it does not go further into authentication or edge-case behavior.

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?

A single, front-loaded sentence communicates the operation and the key return fields without any filler. Every word 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 simple read-only getter with an output schema, two fully documented parameters, and safety annotations, the description is complete. Nothing an agent needs to call it correctly 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%, so the parameters are fully documented in the schema itself. The description adds no extra detail about bucket_name or bucket_token beyond what the schema already provides.

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 uses a specific verb ('Return') and identifies the resource ('bucket details'), then narrows the scope with 'storage and egress usage.' This clearly distinguishes it from sibling tools like get_bucket_permissions, which would handle permission details.

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: use this tool to fetch bucket details plus storage and egress usage. It does not explicitly mention alternatives or exclusions, but the resource and return scope make the use case evident relative to the sibling tool list.

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

All IronShard Object Storage Sandbox 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?