Skip to main content
Glama

Show objective

set_objective_display
Idempotent

Show or clear a Minecraft scoreboard objective in the sidebar, below player names, or in the player list by selecting the display slot.

Instructions

Show an objective in the sidebar, below player names or in the player list, or clear that slot.

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

Input Schema

NameRequiredDescriptionDefault
slotYesWhere on screen to show the objective.
objectiveNoObjective to show; omit to clear the slot.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare mutation (readOnlyHint=false), idempotent=true, and destructiveHint=false; the description usefully adds that the same call can wipe a slot rather than only set it. It does not disclose failure behavior for unknown objective names or any permission/world-state requirements, so added context is modest but not contradictory.

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?

One sentence, front-loaded on the action, with no filler. The trailing 'or clear that slot' phrase is slightly awkward but earns its place by flagging the clearing behavior.

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?

A simple two-parameter mutation with annotations and an output schema present, so return values need not be described. The main gap is that it doesn't say the target objective must already exist or what happens if the slot holds something else.

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 100% and both parameters carry their own descriptions plus an enum for slot, so the schema does the heavy lifting. The description's slot list mirrors the enum without adding format, validation, or default semantics beyond it.

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?

Specific verb+resource: it controls where an objective is displayed, and it enumerates the three possible slots (sidebar, below name, player list). It implicitly distinguishes itself from create_objective/remove_objective by being about display placement rather than existence, though it never names those siblings.

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 'or clear that slot' clause hints at the null path and gives implied usage, but there is no explicit when-to-use guidance, no statement that the objective must already exist, and no routing toward create_objective or show_title.

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