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

@ola/buzz-mcp

Official
by ola-krutrim
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

buzz_profile

Read-onlyIdempotent

Look up a person's profile by npub, hex pubkey, email, or exact display name; returns read-only fields with untrusted text escaped.

Instructions

Look up a person's profile (kind 0) by npub / hex pubkey / email (wire mode) / exact display name. Read-only; profile fields are shown escaped as untrusted text.

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": {
      "user": "<user>"
    },
    "name": "buzz_profile"
  }
}

Input Schema

NameRequiredDescriptionDefault
userYesnpub / hex pubkey / email / exact display name

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.2.36

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the description is not required to restate safety. It does add genuinely new context: profile fields are returned escaped as untrusted text, a security-relevant disclosure an agent needs before acting on returned content, plus the '(wire mode)' caveat for email lookup.

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 primary action and lookup keys are front-loaded and the escaping caveat follows as a short second clause.

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 one-parameter, read-only lookup without an output schema, the description covers how to identify the person and how results should be treated. The only notable gap is that it does not indicate what a failed or ambiguous display-name lookup yields, but that is minor at this complexity.

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 100%, so the single 'user' parameter is fully documented already. The description largely restates the same identifier list, adding only the '(wire mode)' qualifier for email, which is marginal value beyond the schema.

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 specific verb and resource ('Look up a person's profile (kind 0)') and enumerates the accepted key types, so an agent can distinguish it from writing siblings like buzz_profile_set via the 'Read-only' qualifier. It stops short of explicitly naming the sibling it contrasts with, so it is clear rather than exemplary.

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 by 'Read-only' and by the 'exact display name' qualifier, which tells the agent that non-exact names will fail. However, it never states when to prefer this over buzz_profile_set, buzz_whoami, or buzz_agents, nor what happens when the lookup misses.

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