Joy Trust Network

buzz_bind

Map a Buzz/Nostr pubkey to the authenticated Joy agent

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": {
      "pubkey": "<pubkey>"
    },
    "name": "buzz_bind"
  }
}

Input Schema

Name	Required	Description	Default
`pubkey`	Yes	Buzz/Nostr pubkey hex or npub1...
`agent_id`	No	Joy agent id (defaults to API key agent)

Schema Changelog

Changes observed during successful MCP inspections.

AddedAug 17, 2026

TDQS

A3.5/5.0

Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It does not mention whether the mapping is idempotent, overwrites existing mappings, requires specific permissions, or has side effects. The phrase 'authenticated Joy agent' hints at auth context but does not clarify the operation's behavior.

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?

The description is one concise sentence, directly front-loading the action and resource. No redundant or filler words are present.

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?

The tool is simple with two parameters and no output schema, but the description lacks details about return values, side effects, or prerequisites (e.g., authentication required). It barely meets the minimum bar for an agent to understand the operation's context.

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?

The input schema fully describes both parameters (pubkey format and agent_id default), giving a baseline of 3. The description adds no additional meaning beyond repeating the resource names, so it does not compensate or enhance beyond the schema.

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?

The description uses a specific action verb ('Map') and clearly identifies the resource ('Buzz/Nostr pubkey') and destination ('authenticated Joy agent'). It differentiates from sibling tools by focusing on identity binding rather than jobs, deals, or campaigns.

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?

The description implies usage as a mapping step before interacting with Buzz/Nostr, but it does not explicitly state when to use this tool versus alternatives. No exclusions or alternative tool references are provided, leaving the usage context to be inferred.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Joy Trust Network tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?