Skip to main content
Glama

teleport

Move players or entities to specific coordinates or other entities in Minecraft servers using target selectors and coordinate inputs.

Instructions

Teleport a player or entity to coordinates or another entity.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
targetYesTarget selector (e.g., '@a', '@p', 'PlayerName')
xNoX coordinate
yNoY coordinate
zNoZ coordinate
destinationNoDestination entity/player name (alternative to coordinates)

Implementation Reference

  • The handler function for the 'teleport' tool, which constructs and executes the Minecraft 'tp' command.
    async ({ target, x, y, z: zCoord, destination }) => {
      let cmd: string;
      if (destination) {
        cmd = `tp ${target} ${destination}`;
      } else if (x !== undefined && y !== undefined && zCoord !== undefined) {
        cmd = `tp ${target} ${x} ${y} ${zCoord}`;
      } else {
        return {
          content: [
            {
              type: "text",
              text: "Provide either coordinates (x, y, z) or a destination entity.",
            },
          ],
          isError: true,
        };
      }
      try {
        const response = await manager.rcon.send(cmd);
        return { content: [{ type: "text", text: response }] };
      } catch (error) {
  • The Zod schema definition for the 'teleport' tool input parameters.
    {
      target: z
        .string()
        .describe("Target selector (e.g., '@a', '@p', 'PlayerName')"),
      x: z.number().optional().describe("X coordinate"),
      y: z.number().optional().describe("Y coordinate"),
      z: z.number().optional().describe("Z coordinate"),
      destination: z
        .string()
        .optional()
        .describe("Destination entity/player name (alternative to coordinates)"),
    },
  • Registration of the 'teleport' tool with the MCP server.
    server.tool(
      "teleport",
      "Teleport a player or entity to coordinates or another entity.",
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It only describes the intended effect (teleportation) without mentioning error conditions (e.g., invalid coordinates), side effects (e.g., velocity preservation), reversibility, or whether the operation is atomic/safe.

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?

The description is exactly nine words in a single sentence. It is front-loaded with the action verb, mentions the target, and immediately specifies the two destination options without filler words. Every element earns its place.

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?

Given 100% schema coverage, the description adequately covers the input semantics. However, for a 5-parameter tool with no output schema and no annotations, it omits behavioral context (error handling, game state impacts) and does not clarify whether coordinates and destination are mutually exclusive or if both can be provided.

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%, establishing a baseline of 3. The description adds conceptual value by grouping x/y/z as 'coordinates' and identifying 'destination' as an entity alternative, but does not add syntax details, format examples, or semantic constraints (e.g., mutual exclusivity) beyond what the schema provides.

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 clearly states the specific verb (teleport) and resource (player or entity), and distinguishes the two mutually exclusive destination modes (coordinates vs. another entity). However, it does not explicitly differentiate this tool from the sibling 'execute_command' which could also perform teleportation via raw commands.

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 description implies usage by specifying the two alternative destination patterns (coordinate triplet or destination entity), helping the agent understand parameter selection. However, it lacks explicit guidance on when to use this dedicated tool versus alternatives like 'execute_command', and does not state prerequisites or constraints (e.g., that target must be online).

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/tamo2918/Minecraft-Server-MCP'

If you have feedback or need assistance with the MCP directory API, please join our Discord server