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

@ola/buzz-mcp

Official
by ola-krutrim
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

buzz_read

Read-onlyIdempotent

Read recent messages from a Buzz relay channel by name or ID, so agents can catch up on conversation history before responding.

Instructions

Read recent messages in a channel (by name or id).

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

Input Schema

NameRequiredDescriptionDefault
limitNo
channelYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv0.2.36
    • addedInput schema / additionalProperties
      Added value: +false
    • addedInput schema / properties / channel / maxLength
      Added value: +256
    • addedInput schema / properties / limit / maximum
      Added value: +200
    • addedInput schema / properties / limit / minimum
      Added value: +1
  2. First observedv0.2.6

TDQS

B3.1/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and openWorldHint, so the safety profile is fully covered. The description adds that results are 'recent', implying a recency-bounded window, but it does not say the ordering, the default page size, or whether thread replies are included — behavior an agent needs and annotations cannot supply.

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?

One short sentence with zero filler and the resource front-loaded, which is easy to scan. It is arguably undersized for a tool with two fully undocumented parameters, but nothing in the text is wasted.

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

Completeness2/5

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

There is no output schema, so the description is the only place to learn what a returned message looks like and in what order messages arrive — neither is covered. Combined with the unmentioned 'limit', the definition leaves an agent guessing on details that materially affect the call.

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 0%, so the description must carry the burden. It usefully clarifies that 'channel' accepts either a name or an id, which the bare schema does not; however, the 'limit' parameter is never mentioned, leaving its meaning and default undocumented even though the schema caps it at 200.

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 names a clear verb (read) and resource (messages in a channel), plus the scope qualifier 'recent'. It does not distinguish itself from near siblings like buzz_dm_read, buzz_thread_read, or buzz_search, so an agent must infer from the names alone which read tool applies.

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

Usage Guidelines2/5

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

There is no explicit when-to-use or when-not-to-use guidance and no named alternative. An agent is left to infer that this is the channel read path and that buzz_dm_read / buzz_thread_read cover other contexts, which is plausible but not stated.

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