Skip to main content
Glama
ola-krutrim

@ola/buzz-mcp

Official
by ola-krutrim
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

buzz_post

Post a message to a channel, use @Name to mention and trigger agents, and attach local files for sharing.

Instructions

Post a message to a channel. The body goes in text (its alias message is also accepted). Use @Name to mention an agent (resolved to a p-tag so the agent is triggered). Optional attachment = a local file path to upload and attach.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
textNo
channelYes
messageNoalias for `text` (accepted if `text` is omitted)
attachmentNolocal file path to upload + attach (image/doc/video, per-type size caps apply)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.2.7
    • addedInput schema / properties / message
      Added value: +{
+  "description": "alias for `text` (accepted if `text` is omitted)",
+  "type": "string"
+}
    • changedInput schema / required
      Previous value: -[
-  "channel",
-  "text"
-]New value: +[
+  "channel"
+]
  2. First observedv0.2.6

TDQS

A4.2/5.0
Behavior4/5

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

With no annotations, the description carries the behavioral disclosure burden and does useful work: it explains how mentions are resolved (@Name to p-tag, triggering an agent) and what attachment means. It is non-obvious behavior that helps an agent predict side effects, though it does not discuss response values or rate limits.

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, each earns its place: the action, the body/alias behavior, the mention/attachment details. No filler or repetition.

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 simple post tool with no output schema, the description covers the essential behavior, alias, mentions, and attachments. The main gap is lack of guidance for the `channel` parameter format and no explicit routing vs DM/reply tools, but overall it is reasonably complete.

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?

The schema covers `message` and `attachment`, but not `text` or `channel`. The description adds meaning for `text`/`message` and restates the attachment file path, but leaves the required `channel` parameter unspecified (name vs ID). It partially compensates for the 50% schema coverage but not completely.

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?

The description opens with 'Post a message to a channel,' a specific verb and resource that clearly identifies the tool's function. This differentiates it from sibling tools like buzz_dm_send, buzz_reply, and buzz_forward, which cover other messaging actions.

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?

The phrase 'to a channel' establishes the core context and implies this is for channel posts rather than direct messages or replies. It does not explicitly name alternatives or state when not to use it, so it stops short of a 5.

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