Skip to main content
Glama

Teleport entity

teleport_entity
Idempotent

Moves an entity to exact coordinates and optionally sets its facing direction using yaw and pitch.

Instructions

Move an entity to an exact position, optionally setting where it faces.

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

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.
uuidYesEntity UUID, e.g. as returned by summon_entity or get_players.
pitchNoVertical facing in degrees: -90 = straight up, 0 = level, 90 = straight down. Give together with yaw.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=false, idempotentHint=true, and destructiveHint=false, so the safety profile is carried by structured data. The description adds no behavioral context beyond the annotations — nothing about behavior when the target chunk is unloaded, whether cross-dimension moves are allowed, or what occurs if the UUID does not resolve.

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?

One front-loaded sentence with no wasted words and the optional rotation noted up front. It is efficiently sized, though the terseness leaves no room for the routing or failure-mode context that would add value.

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 and annotations cover idempotency and safety, so much is already carried outside the description. Still, for a positional mutation reachable in many contexts, the absence of any note on unloaded chunks, entity validity, or failure behavior is a real gap.

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%, and the schema itself documents coordinate conventions, block-centre offsets, and the yaw/pitch pairing rule in detail. The description contributes nothing beyond it, so 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?

States a specific verb and resource ("Move an entity to an exact position") plus the optional rotation capability. It is clear what the tool does, but it never distinguishes itself from the sibling teleport_player, which likely does the same thing for players.

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?

Contains no when-to-use or when-not-to-use guidance and names no alternatives. An agent cannot tell from this text whether to use teleport_entity, teleport_player, or set_entity_rotation for a given situation.

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