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

@ola/buzz-mcp

Official
by ola-krutrim
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

buzz_dm_send

Send a direct message to one person or a group, opening the 1:1 chat when needed. Use a Nostr identifier, email, or exact display name to reach recipients.

Instructions

Send a direct message to a person — opens the 1:1 if needed, then sends. to = npub / hex / email / exact display-name. The body goes in text (its alias message is also accepted).

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

Input Schema

NameRequiredDescriptionDefault
toYesone person (npub / hex / email / exact display-name) or an array of up to 8 for a group DM
textNo
dry_runNopreview only: resolve everything and show the exact event that would be signed (auth tags redacted) — nothing is signed, uploaded or sent
messageNoalias for `text` (accepted if `text` is omitted)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed8 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 / message / maxLength
      Added value: +65536
    • addedInput schema / properties / text / maxLength
      Added value: +65536
    • 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. 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: -[
-  "to",
-  "text"
-]New value: +[
+  "to"
+]
  3. First observedv0.2.6

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=false, idempotentHint=false and openWorldHint=true; the description adds a real behavioral fact beyond them, namely that the call creates the 1:1 conversation as a side effect if it does not exist. It does not mention duplicate sends creating duplicate messages, permission requirements, or rate limits, which leaves some gaps for a mutation tool.

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 short sentences, front-loaded with the action and side effect, with the parameter hints confined to a compact second sentence. No filler.

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 4-parameter write tool with annotations and no output schema, the description covers what happens, the side effect of conversation creation, and how to address a recipient. Missing details are the preview/dry-run path and the group-DM mode, though both are documented in the schema.

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 75% and the schema already documents the accepted identifier formats for `to` and the `message` alias for `text`, so the description largely restates it. It does not add format examples, character-limit implications, or clarify the discrepancy between 'to a person' and the schema's array-of-up-to-8 group DM case.

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 ('Send a direct message to a person') and adds the distinguishing behavior 'opens the 1:1 if needed, then sends', which separates it from buzz_dm_open (open only) and buzz_post (channel posting). An agent can pick this tool without opening the schema.

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?

Usage is implied rather than stated: the 'opens the 1:1 if needed' clause hints this is the send-in-one-step option, but there is no explicit when-to-use versus buzz_dm_open, buzz_dm_add, or buzz_reply, and no note that a channel conversation should use buzz_post instead.

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