Skip to main content
Glama

cloud_bucket_check

Checks if an S3, GCS, or Azure bucket exists and permits public object listing, returning existence, exposure state, and sample object names for reconnaissance.

Instructions

Check whether an S3/GCS/Azure bucket exists and allows public object listing.

Accepts a bucket name (tries S3 and GCS) or account/container for Azure. Returns existence, public-listing state and a sample of object names. Read-only.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "bucket": "<bucket>"
    },
    "name": "cloud_bucket_check"
  }
}

Input Schema

NameRequiredDescriptionDefault
bucketYes
providerNoauto

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.0

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations present, the description does real work: it declares the tool read-only and describes the return shape (existence, public-listing state, sample object names). It still omits important behavioral details such as whether credentials are required, how the provider auto-detection affects results or latency, and how large the 'sample' of object names is.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two compact sentences, front-loaded with the outcome the tool determines, followed by input and return details. Slightly dense parenthetical about provider probing, but no filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema, the description correctly spends its second sentence on return values, which is valuable. However, for a tool whose behavior varies by provider and input form, the missing explanation of 'provider' and of any authentication requirements leaves the definition short of complete.

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 0%, so the description must compensate. It adds meaningful syntax for 'bucket' (bare name probes S3 and GCS; account/container form targets Azure), but the 'provider' parameter, which defaults to 'auto', is never mentioned, leaving half the inputs undocumented.

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 opens with a specific verb and resource ('Check whether an S3/GCS/Azure bucket exists and allows public object listing'), which is unmistakable and clearly distinct from the neighboring *_check tools (DNSBL, breach, Tor exit), which target entirely different resources.

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?

Usage is implied by the purpose statement and by the note that a bare bucket name tries S3 and GCS while an account/container targets Azure, but there is no explicit when-to-use or when-not-to-use guidance, and no exclusions or prerequisites (credentials, rate limits) are stated.

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