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

@ola/buzz-mcp

Official
by ola-krutrim
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

buzz_join_channel

Idempotent

Join an open Buzz channel by name or UUID; the action is idempotent if already a member, while private channels require an owner/admin invite.

Instructions

Join an OPEN channel yourself (NIP-29 kind 9021). Idempotent — a no-op if you're already a member. Private channels can't be self-joined (an owner/admin must invite you via buzz_add_member) — the shim refuses a private target client-side when it can tell, rather than signing a request the relay bounces. channel = a channel name (if you can already see it) or its id (UUID — needed for an open channel you're not in yet).

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_join_channel"
  }
}

Input Schema

NameRequiredDescriptionDefault
channelYeschannel name or id (UUID)
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

A4.7/5.0
Behavior5/5

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

Goes well beyond the annotations by disclosing the underlying protocol event (NIP-29 kind 9021), the no-op-on-already-member semantics, and the client-side refusal for private targets instead of signing a doomed request. The annotations already declare idempotentHint and destructiveHint=false, and the description reinforces idempotency with a concrete explanation rather than repeating it.

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?

The action and its scope are front-loaded, and each sentence carries a distinct constraint (open-only, idempotency, private refusal, identifier form). The parenthetical protocol jargon and "shim" reference add density that a non-Nostr agent may need to parse, slightly hurting readability.

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 two-parameter mutation tool with no output schema, the description covers the safety profile, targeting rules, and the private-channel failure mode. The only gap is the `dry_run` preview path, which is documented solely in the schema, but that is acceptable given full schema coverage.

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 baseline is 3, but the description adds real meaning: `channel` accepts a name only if the channel is already visible, otherwise a UUID id is required for an open channel not yet joined. That is a decision rule the schema's "channel name or id (UUID)" does not convey. The `dry_run` parameter is left entirely to its schema text.

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 ("Join an OPEN channel yourself") and disambiguates from sibling tools by naming buzz_add_member as the invite path and excluding private channels. An agent can distinguish this from buzz_create_channel, buzz_leave_channel, and buzz_add_member without opening any schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

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

Explicitly states when to use this tool (self-joining an open channel) and when not to (private channels require buzz_add_member), including the fallback behavior when the target is private. It also tells the agent which identifier form to supply depending on whether it can already see the channel.

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