Skip to main content
Glama

Check advancement

get_advancement
Read-onlyIdempotent

Checks whether an online Minecraft player has completed a specified advancement by exact username and advancement ID.

Instructions

Whether an online player has completed an advancement.

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>"
    },
    "name": "get_advancement"
  }
}

Input Schema

NameRequiredDescriptionDefault
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.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is fully covered by structured data. The description adds only the 'online player' constraint, which the schema's own parameter text already states, and says nothing about how a false/absent result is reported.

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 no wasted words, and the key qualifier ('online player') is front-loaded. It is a fragment rather than a statement, and could have spent one more clause on the query framing at no real cost.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists, so return values need not be explained, and both parameters are richly documented. For a simple two-parameter read, however, the description still leaves gaps around offline-player behavior and invalid advancement ids that a one-line definition could have closed.

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%, with both parameters documented including patterns and example advancement ids, so the schema carries the semantic load. The description contributes no additional parameter meaning; 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?

The description names a specific resource — whether a given online player has completed a given advancement — and is clearly distinguishable from the sibling set_advancement. It is a noun-phrase fragment rather than a verb-led statement, so it stops short of an explicit 'check/query' framing, but the intent is unambiguous.

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 guidance on when to use this tool versus alternatives, and no mention of prerequisites or error conditions such as a player being offline or an unknown advancement id. The only implicit cue is the word 'online'.

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