Skip to main content
Glama
ola-krutrim

@ola/buzz-mcp

Official
by ola-krutrim
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

buzz_dm_send

Send a direct message to anyone using their npub, hex, email, or exact display name, auto-opening the 1:1 chat if needed. Put the body in 'text' or 'message'.

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).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
toYes
textNo
messageNoalias for `text` (accepted if `text` is omitted)

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: -[
-  "to",
-  "text"
-]New value: +[
+  "to"
+]
  2. First observedv0.2.6

TDQS

A4.6/5.0
Behavior4/5

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

With no annotations, the description carries the burden of behavioral disclosure. It explicitly reveals a non-obvious side effect: the tool opens the 1:1 conversation automatically if it doesn't exist. This is useful behavioral context beyond the basic 'send' verb, though it doesn't discuss permissions or failure modes.

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 dense sentences with no filler. The action and key behavior are front-loaded, followed by compact parameter guidance. Every clause earns its place.

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

Completeness5/5

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

For a simple 3-parameter tool with no output schema or nested objects, the description covers purpose, recipient resolution, body parameter, alias behavior, and the auto-open side effect. An agent has enough to select and invoke this tool correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is only 33%, but the description compensates well: it explains `to` accepts npub/hex/email/exact display-name, defines `text` as the message body, and clarifies that `message` is an accepted alias. This adds meaning well beyond the raw schema and covers all parameters.

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 action ('Send a direct message to a person') plus the key behavior of opening the 1:1 if needed. This distinguishes it clearly from related tools like buzz_dm_open and buzz_post, so an agent understands what this tool uniquely does.

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 description makes the use case clear: sending a direct message to an individual, with no need to pre-open the conversation. It doesn't explicitly name alternative tools, but the 'to a person' and 'opens the 1:1 if needed' language provides enough contextual guidance for selection.

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