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

@ola/buzz-mcp

Official
by ola-krutrim
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

buzz_channels

Read-onlyIdempotent

Lists your member channels or browses the workspace’s open channels, marking joined ones so you can find and join accessible channels by ID.

Instructions

List channels. Default scope: "member" = the channels you're in. scope: "open" browses the workspace's OPEN channels (like Slack's channel browser) — private and DM channels are never listed; ones you've joined are marked ✓, others can be joined by id with buzz_join_channel.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "buzz_channels"
  }
}

Input Schema

NameRequiredDescriptionDefault
scopeNo"member" (default) or "open"

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.2.36
    • addedInput schema / additionalProperties
      Added value: +false
    • addedInput schema / properties / scope
      Added value: +{
+  "description": "\"member\" (default) or \"open\"",
+  "enum": [
+    "member",
+    "open"
+  ],
+  "maxLength": 16,
+  "type": "string"
+}
  2. First observedv0.2.6

TDQS

A4.7/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive, so the description's added value is behavioral: it discloses the privacy boundary (private and DM channels are never returned), that joined channels are marked ✓, and that unjoined ones can be joined by id — details an agent cannot infer from the schema. No return-format or ordering detail, so not a 5.

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, front-loaded with the default behavior, then the alternative scope and its constraints. No filler and every clause carries information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a one-optional-parameter read tool with no output schema and full annotation coverage, the description supplies everything needed: mode semantics, privacy limits, and the join follow-up path.

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% and the enum is documented, so the baseline is 3; the description goes beyond it by explaining the operational consequence of each scope value (membership list vs. workspace channel browser with ✓ markers), which the schema's terse enum text does not convey.

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 ("List channels") and immediately defines the two scope modes, which is the only thing that distinguishes this tool's output from sibling reads like buzz_dm_list or buzz_channel_members.

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?

Gives explicit when-to-use guidance for both modes: default "member" for your own channels, "open" for browsing the workspace, plus an explicit exclusion (private and DMs are never listed) and a named next-step sibling (buzz_join_channel) for unjoined channels.

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