Skip to main content
Glama

Grant or revoke advancement

set_advancement
DestructiveIdempotent

Grant or revoke a Minecraft advancement for an online player by specifying their exact username, the advancement ID, and whether to award all criteria or clear all progress.

Instructions

Grant or revoke an advancement for an online player.

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": {
      "username": "<username>",
      "advancement": "<advancement>",
      "granted": "<granted>"
    },
    "name": "set_advancement"
  }
}

Input Schema

NameRequiredDescriptionDefault
grantedYesTrue grants every criterion; false revokes all progress.
usernameYesExact, case-sensitive name of an online player.
advancementYesAdvancement id such as 'story/mine_stone' or 'minecraft:adventure/kill_a_mob'.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.1/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=false, destructiveHint=true, and idempotentHint=true, so the safety profile is fully covered elsewhere. The description adds no behavioral context of its own, notably omitting that setting granted=false irreversibly wipes all accumulated criteria progress, which is the main risk an agent should know about.

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 short sentence with the action front-loaded and no filler. Its brevity is appropriate in structure, though it edges toward under-specification rather than excess.

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?

With an output schema, complete parameter documentation, and annotations covering readOnly/destructive/idempotent traits, most of what an agent needs is present in the structured fields. The description itself remains thin, but nothing critical to correct invocation is missing.

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 the meaning of username, advancement, and granted is already fully documented, including the 'true grants every criterion; false revokes all progress' semantics. The description adds nothing beyond that, 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?

Names specific verbs (grant/revoke) and a specific resource (advancement), plus the scope constraint that the target must be an online player. It is distinguishable from the read-only sibling get_advancement by the mutation verb, though no sibling is named explicitly.

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 explicit when-to-use, when-not-to-use, or alternative routing guidance. The only usage constraint, that the player must be online, is already stated in the schema's username description, so the sentence adds no guidance the agent can't get from structured fields.

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