Skip to main content
Glama
Sign In
@ola/buzz-mcp

@ola/buzz-mcp

Official
by ola-krutrim
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

buzz_delete

DestructiveIdempotent

Deletes a specified channel message by channel and event ID, enforcing owner/admin role permissions so only authorized destructive removals proceed.

Instructions

Delete a message in a channel (NIP-29 kind 9005), as you. Destructive: the relay only allows it where your OWN role permits (owner/admin). Identify the message by channel + event (the from buzz_read).

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": {
      "channel": "<channel>",
      "event": "<event>"
    },
    "name": "buzz_delete"
  }
}

Input Schema

NameRequiredDescriptionDefault
eventYesthe target message's <id> (from buzz_read)
channelYes
confirmNoset true to confirm a destructive action (asked once per session per kind in wire / post-as-me mode)
dry_runNopreview only: resolve everything and show the exact event that would be signed (auth tags redacted) — nothing is signed, uploaded or sent

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changedv0.2.36
    • addedInput schema / additionalProperties
      Added value: +false
    • addedInput schema / properties / channel / maxLength
      Added value: +256
    • addedInput schema / properties / confirm
      Added value: +{
+  "description": "set true to confirm a destructive action (asked once per session per kind in wire / post-as-me mode)",
+  "type": "boolean"
+}
    • addedInput schema / properties / dry_run
      Added value: +{
+  "description": "preview only: resolve everything and show the exact event that would be signed (auth tags redacted) — nothing is signed, uploaded or sent",
+  "type": "boolean"
+}
    • addedInput schema / properties / event / maxLength
      Added value: +128
  2. Addedv0.2.7

TDQS

A4/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true, idempotentHint=true and openWorldHint=true, so the safety profile is largely covered. The description adds genuine value beyond them by disclosing the role-based authorization gate and the actor scope ('as you'), but says nothing about what happens after a successful delete or how relay rejection surfaces.

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, no filler, with the destructive nature and the permission constraint front-loaded before the identification instructions. Every clause carries information an agent needs.

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 destructive four-parameter tool with no output schema, the description covers the essential risks: what it deletes, under whose authority, and how to target it. The remaining details (confirm/dry_run behavior) live in the schema, so nothing critical is missing, though post-call outcomes are unaddressed.

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 75%, so the schema already explains event, confirm and dry_run, and the description's 'channel + event' restates the event parameter's own text nearly verbatim. No new meaning is added for the two optional flags, so the baseline of 3 for high-coverage schemas 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 ('Delete a message in a channel'), pins it to protocol semantics (NIP-29 kind 9005), and scopes it to acting 'as you', which separates it from channel-level deletion (buzz_delete_channel) and from buzz_edit_message 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 Guidelines4/5

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

Gives a real prerequisite: the relay only permits deletion where the caller's own role is owner/admin, and tells the agent where the target identifier comes from ('the <id> from buzz_read'). It stops short of naming an alternative to use when deletion is not permitted, so it is clear context rather than a full when/when-not rule set.

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