Skip to main content
Glama

Grant or revoke advancements

set_advancement
Idempotent

Mark all criteria of specified Minecraft advancements as completed for an online player, or revoke them by setting done to false; returns player_offline if the player is not connected.

Instructions

Complete every criterion of advancements for a player (done true), or take them all back (done false). The player must be online; otherwise the error is player_offline.

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": {
      "player": "<player>",
      "keys": "<keys>",
      "done": "<done>"
    },
    "name": "set_advancement"
  }
}

Input Schema

NameRequiredDescriptionDefault
doneYesfalse revokes
keysYesAdvancement keys, such as ["minecraft:story/mine_diamond"]
playerYesPlayer name or UUID

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv4.2.1
    • addedInput schema / properties / done / description
      Added value: +"false revokes"
  2. First observedv4.1.0

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare the mutation profile (readOnlyHint=false, idempotentHint=true, destructiveHint=false), so credit goes to the added context: the player must be online and the failure surfaces as `player_offline`. It stops short of describing what happens with unknown keys, partial success, or whether revoking wipes earned criteria irrecoverably.

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 sentences, zero filler, with the primary operation front-loaded and the precondition/error trailing. Every clause carries information an 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?

For a three-parameter mutation tool with no output schema, the description covers the core semantics, the precondition, and one error code. It is nearly complete; only edge behavior (invalid keys, repeat calls, effect on already-completed criteria) is left unstated.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3, but the description adds genuine semantics the schema lacks: done=true completes *every criterion* rather than flipping a single flag, and done=false retracts them all at once. Player and keys semantics remain schema-only, which is fine given full coverage.

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 (complete/take back) applied to a specific resource (advancements for a player), and the parenthetical maps each boolean value to its effect. It does not need sibling differentiation because no sibling operates on advancements, but it also never explicitly says what 'advancement' means in this server context.

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 by the done=true/done=false mapping and by the explicit online requirement, which is a real precondition. There is no explicit guidance on when to prefer this tool over manual per-criterion progression or what to do for an offline player beyond the error name.

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