Skip to main content
Glama

Get experience

get_experience
Read-onlyIdempotent

Retrieve an online Minecraft player's experience by username to see their level, total points, and progress toward the next level.

Instructions

An online player's experience: level, total points and progress (0-1) toward the next level.

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

Input Schema

NameRequiredDescriptionDefault
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

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 elsewhere. The description adds genuine value in describing the shape of the result, notably that progress is normalized to 0-1 and that points are a total, which an agent cannot infer from the annotations. It says nothing about behavior for unknown or offline players, but with annotations carrying the mutation semantics this is adequate.

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 tight sentence with no filler, and the fields are listed up front. It is a noun phrase rather than a complete clause, which slightly weakens the opening, but no word is wasted.

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 one-parameter read with full annotations and an output schema, the description covers what the tool returns and the scale of the progress value. It omits error behavior for nonexistent players, which is a minor gap given the output schema presumably defines the success shape.

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%; the single username parameter is fully documented in-schema including case-sensitivity, length bounds, and pattern. The description adds no meaning beyond that, and the baseline of 3 applies when the schema does all the parameter work.

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 the resource precisely (an online player's experience) and enumerates the returned fields: level, total points, and progress toward next level. The retrieval intent is clear from the resource framing and the 'get_' prefix, but the sentence has no verb and makes no explicit contrast with the sibling update_experience, which is the tool an agent could most plausibly confuse it with.

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 when-to-use guidance, no prerequisite, and no mention of the mutating alternative update_experience. The only signal an agent gets is implicit: it is a read of experience data. That is not enough to route between get_experience, get_advancement, and get_score, which plausibly overlap in scope.

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