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

@ola/buzz-mcp

Official
by ola-krutrim
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

buzz_channel_topic

Idempotent

Set or clear a channel's topic or purpose for owner/admins, with relay-enforced permissions. Use an empty string to clear either field.

Instructions

Set or clear a channel's topic and/or purpose (kind 9002, owner/admin only — relay-enforced). Empty string clears.

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

Input Schema

NameRequiredDescriptionDefault
topicNonew topic (≤500 chars; empty clears)
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
purposeNonew purpose (≤500 chars; empty clears)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.2.36

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare non-read-only, idempotent and non-destructive; the description adds value beyond them by disclosing the relay-enforced owner/admin permission gate and the wire kind (9002), which the agent cannot learn from the schema. It does not explain whether the change is announced to channel members or what the response looks like, so it is not fully complete.

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?

A single sentence carries the action, scope, permission constraint and clearing rule, with the primary action front-loaded and zero 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 mutation tool with full schema coverage and existing annotations, the description covers the permission gate and the clear-value convention, which are the two things an agent most needs. It omits return/response behavior and the interaction with the confirm/dry_run parameters, which are documented in the schema instead.

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 description coverage is 100%, so the schema already documents every parameter including the empty-string-clears semantics, which the description partially restates. The only added meaning is "and/or", implying either or both fields may be supplied in one call, which is marginal over the schema.

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 specific verb pair ("Set or clear") bound to a precise resource ("a channel's topic and/or purpose"), which is enough to separate it from the broader buzz_edit_channel sibling. It stops short of naming that sibling explicitly, so differentiation is inferred from the resource rather than stated.

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 prerequisite "owner/admin only — relay-enforced" is a genuine when-can-I-use condition, and "Empty string clears" indicates the clearing use case. However, there is no guidance on when to pick this over buzz_edit_channel for channel metadata, and no mention of what happens if both topic and purpose are omitted.

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