Skip to main content
Glama
zeeweebee

Minecraft MCP Server

by zeeweebee

move-to-position

Teleport a Minecraft bot to specified coordinates with adjustable arrival precision. Use this tool to position characters at exact X, Y, Z locations for navigation, building, or exploration tasks.

Instructions

Move the bot to a specific position

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
xYesX coordinate
yYesY coordinate
zYesZ coordinate
rangeNoHow close to get to the target (default: 1)

Implementation Reference

  • The handler function for the 'move-to-position' tool. It creates a pathfinder GoalNear to the specified (x,y,z) within the given range and executes bot.pathfinder.goto(goal).
    async ({ x, y, z, range = 1 }): Promise<McpResponse> => {
      try {
        const goal = new goals.GoalNear(x, y, z, range);
        await bot.pathfinder.goto(goal);
    
        return createResponse(`Successfully moved to position near (${x}, ${y}, ${z})`);
      } catch (error) {
        return createErrorResponse(error as Error);
      }
    }
  • Zod input schema for the 'move-to-position' tool parameters: x, y, z (required numbers), range (optional number).
    {
      x: z.number().describe("X coordinate"),
      y: z.number().describe("Y coordinate"),
      z: z.number().describe("Z coordinate"),
      range: z.number().optional().describe("How close to get to the target (default: 1)")
    },
  • src/bot.ts:174-193 (registration)
    Registration of the 'move-to-position' tool using McpServer.tool(), within the registerPositionTools function.
    server.tool(
      "move-to-position",
      "Move the bot to a specific position",
      {
        x: z.number().describe("X coordinate"),
        y: z.number().describe("Y coordinate"),
        z: z.number().describe("Z coordinate"),
        range: z.number().optional().describe("How close to get to the target (default: 1)")
      },
      async ({ x, y, z, range = 1 }): Promise<McpResponse> => {
        try {
          const goal = new goals.GoalNear(x, y, z, range);
          await bot.pathfinder.goto(goal);
    
          return createResponse(`Successfully moved to position near (${x}, ${y}, ${z})`);
        } catch (error) {
          return createErrorResponse(error as Error);
        }
      }
    );

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.9/5.0
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. 'Move' implies a physical action, but the description doesn't specify whether this requires specific conditions (e.g., game mode, permissions), what happens if the position is unreachable, or any side effects like collision or pathfinding behavior. This is a significant gap for a movement tool with zero annotation coverage.

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 a single, efficient sentence with zero waste. It's front-loaded and appropriately sized for the tool's purpose, making it easy to parse quickly.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the complexity of a movement tool with no annotations and no output schema, the description is incomplete. It doesn't explain what 'move' entails (e.g., walking, flying, teleporting), success/failure conditions, or return values, leaving critical behavioral aspects undocumented.

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%, so the schema already documents all parameters (x, y, z, range) with descriptions. The description adds no additional meaning beyond implying coordinate-based movement, which is already clear from the parameter names. Baseline 3 is appropriate when the schema does the heavy lifting.

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 verb ('move') and resource ('the bot'), specifying the action and target. However, it doesn't distinguish this tool from sibling tools like 'move-in-direction' or 'fly-to', which also involve movement, so it lacks sibling differentiation.

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?

The description provides no guidance on when to use this tool versus alternatives like 'move-in-direction' or 'fly-to'. It doesn't mention prerequisites, exclusions, or specific contexts, leaving the agent to infer usage from the name alone.

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