Skip to main content
Glama

Remove boss bar

remove_bossbar
DestructiveIdempotent

Deletes a boss bar by its ID and hides it from all players, removing the specified bar from the Minecraft server display.

Instructions

Delete a boss bar and hide it from everyone.

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

Input Schema

NameRequiredDescriptionDefault
bar_idYesBoss bar id (no spaces).

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true, idempotentHint=true and readOnlyHint=false, so the mutation profile is known. The description contributes one real behavioral detail beyond that: the removal applies globally ("from everyone"), not just to the caller. It does not address what happens to players currently viewing the bar or whether deletion is recoverable.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single front-loaded sentence with no filler; the effective scope is stated up front. It is sized appropriately for a one-parameter tool, though the trailing clause borders on restating the deletion.

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?

The tool is simple, its single required parameter is fully documented, an output schema exists so return values need not be explained, and annotations cover safety and idempotency. Only the caller-facing edge cases (missing bar id, viewers) remain unaddressed, which 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%: bar_id is documented with format constraints (no spaces, 1-64 chars, pattern). The description adds no meaning about the identifier, so the baseline 3 applies.

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?

"Delete a boss bar" is a specific verb plus resource, and the verb cleanly separates it from create_bossbar and update_bossbar without naming them. The added "hide it from everyone" reinforces the effect but is not needed to establish purpose.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no statement of when to use this versus update_bossbar (e.g. hiding rather than deleting) or versus other remove_* siblings. The intent is inferable from the verb, but no conditions or exclusions are given.

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