Skip to main content
Glama

Create boss bar

create_bossbar

Creates an in-memory boss bar with custom title, color, style, and progress, then shows it to specified online players; bars disappear on server restart.

Instructions

Create a boss bar and show it to the given players. Bars live in the plugin's memory: they are separate from vanilla /bossbar and disappear when the server restarts.

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": "create_bossbar"
  }
}

Input Schema

NameRequiredDescriptionDefault
colorNoBar colour; default white.
styleNoSolid or segmented; default solid.
titleNoText shown above the bar; default: the id.
bar_idYesBoss bar id (no spaces).
playersNoOnline player names.
visibleNoWhether the bar is shown; default true.
progressNoFill level 0-1; default 1.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly=false, destructive=false, openWorld=false, idempotent=false), and the description adds real behavioral context beyond them: the bar is stored in plugin memory only, is distinct from vanilla /bossbar, and vanishes on server restart. It omits what happens when bar_id already exists, which matters for a non-idempotent create with a caller-supplied key.

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 short sentences, zero padding, with the core action front-loaded and the persistence caveat immediately after it. Every clause carries information the agent would otherwise have to guess.

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?

An output schema exists and the input schema is fully annotated, so the description need not explain return values or parameters. The gap is the unspecified collision behaviour for an existing bar_id and any permission prerequisites; the persistence and vanilla-separation notes otherwise make it complete for a simple create.

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 colours, styles, title default, progress range and player-name format are all documented in structured fields. The description only echoes 'given players' and adds no syntax or constraint detail beyond the schema, which is the expected baseline when the schema does the work.

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?

States a specific verb and resource ('Create a boss bar') plus the immediate side effect ('show it to the given players'), so the agent knows this both registers and displays. It also delimits scope against vanilla /bossbar. It does not explicitly say how it differs from the sibling update_bossbar, so sibling differentiation is only partial.

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 rather than stated: the agent can infer this is the right call for a brand-new bar, and the 'lives in plugin memory / separate from vanilla /bossbar' note hints at the ephemeral nature. There is no explicit when-not guidance and no mention of reaching for update_bossbar or remove_bossbar instead.

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