Skip to main content
Glama

Update boss bar

update_bossbar
Idempotent

Modify a Minecraft boss bar's color, style, title, progress, visibility, and visible players; omitted settings remain unchanged.

Instructions

Change a boss bar's look or progress and who sees it; omitted settings are left alone.

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

Input Schema

NameRequiredDescriptionDefault
colorNoNew colour.
styleNoNew style.
titleNoNew title.
bar_idYesBoss bar id (no spaces).
visibleNoShow or hide the bar.
progressNoNew fill level 0-1.
add_playersNoOnline player names.
remove_playersNoOnline player names.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, idempotentHint=true, and destructiveHint=false, so the mutation safety profile is covered. The description adds valuable behavioral context about partial updates ('omitted settings are left alone') and scope of visibility changes, but it does not mention permissions, rate limits, or return behavior beyond what the output schema provides.

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 single sentence is front-loaded with the core action and includes the key differentiator about omitted settings. No unnecessary wording or repetition is present.

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?

Given moderate complexity (8 parameters, partial update semantics) and rich structured data (full schema coverage, annotations, output schema), the description covers the essential partial-update behavior. It could explicitly state when to use this over create/remove, but for an update tool with complete schema and annotations, it is nearly complete.

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 all eight parameters are documented in the input schema. The description does not add any parameter-specific semantics like syntax, format, or edge cases beyond what the schema already provides, making the baseline 3 appropriate.

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 clearly states a specific verb 'Change' and resource 'boss bar', and specifies the aspects being modified: looks, progress, and visibility. The clause 'omitted settings are left alone' distinguishes it from create/remove siblings by highlighting partial update semantics.

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 for modifying an existing boss bar but offers no explicit when-to-use guidance, no exclusions, and does not name alternatives like create_bossbar or remove_bossbar. The context is clear enough to infer the tool's role, but not directive.

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