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

@ola/buzz-mcp

Official
by ola-krutrim
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

buzz_delete_channel

DestructiveIdempotent

Permanently delete a Buzz relay channel as its owner. Requires confirm: true; runs with the agent key and is unavailable in wire or post-as-me mode.

Instructions

Permanently delete a channel (kind 9008; owner only — relay-enforced). Always needs confirm: true. Not available in wire / post-as-me mode (Ekam deliberately doesn't sign kind 9008) — agent key 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": {
      "channel": "<channel>"
    },
    "name": "buzz_delete_channel"
  }
}

Input Schema

NameRequiredDescriptionDefault
channelYeschannel name or id
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. Addedv0.2.36

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already mark the tool destructive, idempotent and open-world; the description adds the key behavioral context that deletion is permanent, relay-enforced owner-only, requires confirm, and is unavailable in wire/post-as-me modes. It does not describe downstream effects on channel content/members or error behavior, but it adds substantial context beyond annotations.

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?

Three short sentences, front-loaded with the core action and then constraints; the parenthetical about kind 9008/Ekam is useful context rather than filler.

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 3-parameter tool with rich annotations and no output schema, the description covers permanence, authorization, confirmation and mode availability. It could say more about what happens to channel messages/members, but the essential invocation context is present.

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

Parameters4/5

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

Schema coverage is 100%, so the schema documents channel, confirm and dry_run. The description still adds meaningful semantics by saying confirm is always required, which is not reflected in the required array, though it does not elaborate on channel resolution or dry_run.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description gives a precise verb and resource ('Permanently delete a channel') plus owner-only and kind 9008 scope. It does not name buzz_archive_channel or buzz_leave_channel, so the distinction from those siblings is left implicit rather than explicit.

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?

It supplies important execution constraints (owner only, confirm true, unavailable in wire/post-as-me mode) but never states when an agent should choose this over archive_channel or leave_channel. Usage is therefore implied by 'permanently delete' rather than routed to alternatives.

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