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

@ola/buzz-mcp

Official
by ola-krutrim
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

buzz_dm_open

Idempotent

Open or find a direct-message channel for one person or up to eight recipients by npub, hex, email, or exact display name and return its channel ID.

Instructions

Open (or find) a 1:1 DM with a person and return its channel id. to = npub / hex / email / exact display-name.

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": {
      "to": "<to>"
    },
    "name": "buzz_dm_open"
  }
}

Input Schema

NameRequiredDescriptionDefault
toYesone person (npub / hex / email / exact display-name) or an array of up to 8 for a group DM
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. Changed6 schema fields changedv0.2.36
    • addedInput schema / additionalProperties
      Added value: +false
    • addedInput schema / properties / dry_run
      Added value: +{
+  "description": "preview only: resolve everything and show the exact event that would be signed (auth tags redacted) — nothing is signed, uploaded or sent",
+  "type": "boolean"
+}
    • addedInput schema / properties / to / description
      Added value: +"one person (npub / hex / email / exact display-name) or an array of up to 8 for a group DM"
    • addedInput schema / properties / to / items
      Added value: +{
+  "type": "string"
+}
    • addedInput schema / properties / to / maxItems
      Added value: +8
    • changedInput schema / properties / to / type
      Previous value: -"string"New value: +[
+  "string",
+  "array"
+]
  2. First observedv0.2.6

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, idempotentHint=true, destructiveHint=false, and openWorldHint=true. The description adds useful confirmation that an existing DM is found rather than duplicated ('or find') and that a channel id is returned, but says nothing about what happens when the recipient can't be resolved, whether authentication is required, or what the group-DM path does.

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?

Two short fragments, front-loaded with the action and the return value. The trailing `to` format list is redundant against the schema's identical enumeration and could be dropped without losing information.

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

Completeness3/5

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

For a two-parameter tool the description covers the core promise (find-or-create, return channel id) and the annotations carry the safety profile. It omits the group-DM mode the schema supports and any failure behavior for unresolvable identities, which matters for an open-world tool where resolution can fail.

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 both properties carry descriptive text that is richer than the description's (the schema explains arrays of up to 8 for group DMs and the dry_run preview semantics in detail). The description's `to` = npub / hex / email / exact display-name merely restates the schema, so the baseline of 3 applies.

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?

States a specific verb and resource ('Open (or find) a 1:1 DM') plus the return value ('channel id'), which clearly separates it from siblings like buzz_dm_send, buzz_dm_read, and buzz_dm_list. The word '1:1' undersells it, since the schema allows an array of up to 8 recipients for a group DM, so the stated purpose is narrower than the tool's actual capability.

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?

'Open (or find)' implies this is the idempotent setup step that produces a channel id for a subsequent buzz_dm_send, but the description never states that workflow explicitly. It names no alternative (buzz_dm_add, buzz_dm_list) and gives no condition for choosing between them.

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