Skip to main content
Glama

Change experience

update_experience

Add or set an online player's Minecraft experience in points or levels; when setting points, adjust progress within the current level rather than total points.

Instructions

Add or set an online player's experience. Note: mode='set' with unit='points' sets the progress bar within the current level (amount / points needed for the next level), not the total points.

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

Input Schema

NameRequiredDescriptionDefault
modeNoAdd to or replace the current value.add
unitNoWhether amount is in points or levels.points
amountYesAmount to add or set.
usernameYesExact, case-sensitive name of an online player.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnlyHint=false, idempotentHint=false, destructiveHint=false), and the description adds genuinely useful behavioral context the schema does not: that mode='set' with unit='points' targets progress within the current level rather than total points. It stops short of stating what happens on level-up overflow or when the named player is offline.

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 short sentences with the primary action front-loaded and the caveat immediately after it. Every clause carries information that is not duplicated in the schema or annotations.

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?

Output schema exists, so return values need no explanation. For a 4-param mutation on a live player, the definition covers the main semantic trap; only permission requirements and out-of-range/offline-player behavior are 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 baseline would be 3; the description earns above baseline by clarifying the non-obvious interaction between mode and unit — semantics the enum descriptions do not capture. It does not address negative amounts or the 1,000,000 bounds, but the core ambiguity is resolved.

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 and resource: 'Add or set an online player's experience.' That clearly identifies the operation and its target, and the add/set duality is expanded later; however, it never explicitly distinguishes itself from the sibling get_experience or explains the add-vs-set choice up front.

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 only implied by the verb framing. There is no explicit when-to-use guidance, no statement of prerequisites (player must be online, permissions required), and no mention of the read counterpart get_experience as the alternative for inspecting values.

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