Skip to main content
Glama
Sign In
google-cloud-console-mcp

google-cloud-console-mcp

by kutleloove
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Delete bucket

gcs_delete_bucket

Deletes an empty Google Cloud Storage bucket. Remove all objects first using gcs_delete_object.

Instructions

Deletes an empty bucket. Delete all objects in it first with gcs_delete_object.

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": "gcs_delete_bucket"
  }
}

Input Schema

NameRequiredDescriptionDefault
bucketYesBucket name (without gs:// prefix)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.2/5.0
Behavior4/5

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

With no annotations, the description carries the burden and does disclose a real behavioral constraint that would otherwise cause a failed call: the bucket must already be empty. It omits irreversibility and required permissions/scope, which are the highest-value facts for a destructive operation, so it stops short of a 5.

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 short sentences, no waste, with the defining constraint front-loaded and the prerequisite tool named second. Every clause earns its place.

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?

For a one-parameter destructive tool with no output schema, the description covers the essential precondition and the dependency on gcs_delete_object. The remaining gap is the lack of an irreversibility/permission warning, which would be the only other thing an agent needs before calling it.

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 coverage is 100% and the single 'bucket' parameter is fully documented in the schema (including the no-gs:// prefix rule). The description adds no parameter-level detail beyond what the schema already provides, so the baseline 3 applies.

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 ('Deletes an empty bucket') and pins the scope with the emptiness constraint, which distinguishes it from gcs_delete_object. An agent immediately knows what the call does and what it does not accept.

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?

Gives the operative precondition (bucket must be empty) and routes to the sibling tool for the preceding step ('Delete all objects in it first with gcs_delete_object'). It does not state exclusions or alternatives for other cases, but the context is clear.

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

Deploy Server

Other Tools