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

@ola/buzz-mcp

Official
by ola-krutrim
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

buzz_setname

Idempotent

Set or override this session's friendly display name on the fleet in agent mode, so other agents see the intended name. Deprecated alias of buzz_profile_set.

Instructions

DEPRECATED alias of buzz_profile_set { name } — override this session's friendly display name on the fleet. Agent mode only.

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

Input Schema

NameRequiredDescriptionDefault
nameYes
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. Changed3 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 / name / maxLength
      Added value: +400
  2. 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 idempotentHint=true, destructiveHint=false and openWorldHint=true, so the description earns credit for adding scope that structure does not convey: the change applies only to this session's display name, and the tool is restricted to agent mode. It does not mention the available dry_run preview path, which is the main behavioral omission.

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?

A single sentence with the most important fact — DEPRECATED — front-loaded, followed by the canonical replacement and the operational constraint. No filler, no restatement of the tool title.

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 two-parameter deprecated alias with no output schema and full annotation coverage, this is nearly complete: replacement target, scope of effect, and mode restriction are all stated. The only shortfall is that dry_run — a non-obvious capability present in the schema — goes unmentioned, which matters slightly more here than for a fully documented tool.

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 50%: dry_run is well documented in the schema while name has no description at all. The description compensates for name by tying it to the session's friendly display name (and the { name } notation signals the mapping), but says nothing about the 400-character limit or about dry_run, leaving the remaining coverage gap partly unaddressed. Baseline 3 is appropriate.

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 the exact operation ('override this session's friendly display name on the fleet') and identifies itself as a deprecated alias of buzz_profile_set, which is a specific verb+resource. It is slightly less crisp than a primary tool definition because the core statement is framed as an alias rather than a standalone action, but an agent can still tell exactly what it does and what it maps to.

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?

'DEPRECATED alias of buzz_profile_set' plus 'Agent mode only' gives an agent both a routing signal toward the canonical sibling and a precondition for use. What is missing is an explicit instruction such as 'prefer buzz_profile_set instead' and any statement of what happens if called outside agent mode, but the practical guidance is clear.

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