Skip to main content
Glama

Get player position

get_player_position
Read-onlyIdempotent

Retrieve the block position of an online Minecraft player's feet, rounded down, to identify the block beneath them.

Instructions

Block position of an online player's feet (rounded down); the block they stand on is at y - 1.

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_player_position"
  }
}

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

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world, so the safety profile is covered. The description adds real behavioral detail beyond them: the value is a block coordinate rounded down, and the supporting block is at y - 1, which prevents off-by-one misuse. It does not say what happens for an offline or unknown player, which is the remaining gap.

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?

One sentence, front-loaded with the returned quantity, with the rounding rule and the y - 1 relationship packed in without a wasted word.

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 present and rich annotations, the description only needs to pin down the semantics of the returned coordinate, which it does explicitly. The only omission is failure behavior for offline or misspelled usernames, a minor but real gap for a lookup keyed on an exact online-player name.

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% and the single parameter is documented as the exact, case-sensitive name of an online player. The description only echoes the "online player" constraint and adds no format or matching detail beyond the schema, so the baseline of 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 the exact resource and the precise quantity returned: the block position of an online player's feet, rounded down. That is specific enough to separate it from get_players (roster) and teleport_player (movement), though the verb is implied rather than stated.

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?

The phrase "online player's" implicitly states the prerequisite that the target must be online, which is useful qualifying context. However, there is no explicit when-to-use guidance and no alternatives are named for related lookups such as entity position or chunk/block queries.

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