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);
        }
      }
    );
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states the action ('move') but lacks details on permissions, rate limits, side effects (e.g., pathfinding, obstacles), or response behavior. This is inadequate for a mutation 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 no wasted words, making it front-loaded and easy to parse. It directly conveys the core action without unnecessary elaboration.

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 cover behavioral aspects like success/failure conditions, error handling, or interaction with the environment (e.g., obstacles), leaving significant gaps for agent understanding.

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 fully documents parameters (x, y, z, range). The description adds no meaning beyond the schema, as it doesn't explain coordinate systems, units, or range implications. Baseline 3 is appropriate when the schema handles parameter documentation.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description 'Move the bot to a specific position' clearly states the action (move) and target (bot), but it's vague about the context (e.g., in a game or simulation) and doesn't differentiate from sibling tools like 'fly-to' or 'move-in-direction'. It provides a basic purpose without specificity or sibling distinction.

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?

No guidance is provided on when to use this tool versus alternatives such as 'fly-to' or 'move-in-direction'. The description implies movement to coordinates but doesn't specify contexts, prerequisites, or exclusions, leaving the agent without usage direction.

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/zeeweebee/mcp-server'

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