Skip to main content
Glama

Teleport player

teleport_player
Idempotent

Moves an online Minecraft player to exact X, Y, Z coordinates in their current world, with optional yaw and pitch to set facing.

Instructions

Teleport an online player within their current world, optionally setting where they face.

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>",
      "x": "<x>",
      "y": "<y>",
      "z": "<z>"
    },
    "name": "teleport_player"
  }
}

Input Schema

NameRequiredDescriptionDefault
xYesExact X; block centres are at .5 (e.g. 100.5).
yYesExact Y of the feet.
zYesExact Z; block centres are at .5 (e.g. -20.5).
yawNoHorizontal facing in degrees: 0 = south, 90 = west, 180 = north, 270 (or -90) = east. Give together with pitch.
pitchNoVertical facing in degrees: -90 = straight up, 0 = level, 90 = straight down. Give together with yaw.
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.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, idempotentHint=true, so the mutation/idempotency profile is covered. The description adds useful scope (current-world only, target must be online) but says nothing about failure behaviour for offline or unknown usernames, and no pagination/return detail beyond the output schema.

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 front-loaded sentence with no filler. It is efficient, though the terseness leaves little room for the scope cues an agent would benefit from.

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 full schema coverage, an output schema, and annotations covering safety and idempotency, the description supplies the two facts the structured fields do not: the target must be online and the teleport is confined to the current world. Only error/edge-case behaviour is absent, which is minor at this complexity.

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 each parameter already documents ranges, coordinate conventions, and the yaw/pitch pairing rule. The description's "optionally setting where they face" merely restates that yaw/pitch are optional, adding no meaning 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?

States a specific verb+resource ("Teleport an online player") and adds a meaningful scope constraint: the move happens only "within their current world." That distinguishes it from a cross-world transfer and from the entity variant, even though teleport_entity is not 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 Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is only implied: the target must be an online player and the destination stays in the current world. There is no explicit when-to-use/when-not guidance and no mention of the sibling teleport_entity for non-player targets or get_player_position for locating a player first.

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