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

@ola/buzz-mcp

Official
by ola-krutrim
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

buzz_dm_hide

DestructiveIdempotent

Hide a 1:1 direct message from the DM list by channel ID or the other participant, keeping unwanted conversations out of view.

Instructions

Hide a DM conversation from your DM list (kind 41012). Identify it by channel (dm id) or to (the other person of a 1:1). Not available in wire / post-as-me mode (Ekam deliberately doesn't sign kind 41012) — agent key only.

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

Input Schema

NameRequiredDescriptionDefault
toNothe other person of a 1:1 DM
channelNothe DM's channel id
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.2/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true, idempotentHint=true and openWorldHint=true, so the safety profile is covered. The description adds genuinely non-derivable behavior: the event kind 41012 and the hard auth constraint that only an agent key can perform it. It still leaves open whether hiding is reversible and what happens to the conversation's messages.

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 tight sentences with the action and effect front-loaded, then identification, then the mode restriction. Nothing is padded and no sentence is redundant.

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 zero-required-param mutation with full schema coverage and no output schema, the description covers purpose, addressing and the auth-mode limitation well. The remaining gap is the consequence of hiding, in particular whether it can be undone, which matters given destructiveHint=true.

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 coverage is 100% and the parameter descriptions ('the other person of a 1:1 DM', 'the DM's channel id') are nearly restated verbatim. The one addition beyond the schema is framing `channel` and `to` as alternative identification routes, which is modest value but not required context since `dry_run` is already fully documented.

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 with the resulting effect: 'Hide a DM conversation from your DM list (kind 41012)'. That cleanly separates it from buzz_dm_list, buzz_dm_read, buzz_dm_open and buzz_dm_send, which act on the same resource but do different things.

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?

Gives real usage context by naming the two acceptable identification paths (`channel` for a dm id, `to` for the counterpart in a 1:1) and an explicit when-not: unavailable in wire / post-as-me mode because Ekam doesn't sign kind 41012. It stops short of routing the agent to a sibling (e.g. how this differs from buzz_delete or whether a hidden DM can be restored).

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