Skip to main content
Glama
Sign In
MCP Hub

MCP Hub

by airano-ir
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Cloudflare: Delete kv namespace

cloudflare_delete_kv_namespace
Destructive

Permanently deletes a Cloudflare Workers KV namespace and all its keys, requiring Workers KV Storage Edit permission. Use to remove obsolete storage and prevent further reads or writes.

Instructions

[UNIFIED] Delete a KV namespace and ALL its keys (Workers KV Storage Edit permission). DESTRUCTIVE — every key in the namespace is permanently lost.

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": {
      "site": "<site>",
      "namespace_id": "<namespace_id>"
    },
    "name": "cloudflare_delete_kv_namespace"
  }
}

Input Schema

NameRequiredDescriptionDefault
siteYes
account_idNo
namespace_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv3.14.0

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true, readOnlyHint=false, and idempotentHint=false, so the safety profile is covered. The description adds real value beyond that: it names the specific consequence (every key in the namespace is permanently lost) and the permission required to invoke it. It stops short of describing failure behavior or the response, which keeps it at a 4.

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 short sentences, front-loaded with the action and its scope, then the destruction warning. The "[UNIFIED]" prefix is system noise that does not help an agent, but it is minor against otherwise tight phrasing.

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?

Safety information is complete between the annotations and the explicit blast-radius warning, and no output schema means return values do not need explaining. However, for a destructive tool whose inputs are entirely undocumented in the schema, leaving `site` and `account_id` unexplained is a real gap.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description carries the full burden for three parameters. It only gestures at namespace_id via "a KV namespace" and says nothing at all about the required `site` parameter or the optional `account_id`, leaving the agent to guess what `site` means.

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?

"Delete a KV namespace and ALL its keys" states a specific verb, a specific resource, and the blast radius. The emphasis on "ALL its keys" implicitly separates it from cloudflare_delete_kv_key, so an agent can route between the two without opening either schema.

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 description identifies the required permission (Workers KV Storage Edit) which is useful context, but it never states when to choose this over cloudflare_delete_kv_key or when deletion is inappropriate. Usage is implied by the tool name rather than spelled out.

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