Skip to main content
Glama
deenesjakoruzh
nacal

MCP Minecraft Remote

by nacal
OverviewSchemaRelated ServersScoreDiscussions
TypeScript
Remote

moveTo

Teleport a player to specified coordinates in Minecraft, enabling precise navigation and location management for remote server control.

Instructions

Move the player to a specific location

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
xYesX coordinate
yYesY coordinate
zYesZ coordinate

Implementation Reference

  • src/tools/movement.ts:46-86 (handler)
    The handler function for the 'moveTo' tool. It configures the bot's pathfinder movements and sets a GoalBlock to the target coordinates, handling success, errors, and a 60-second timeout.
    async ({ x, y, z }) => {
  if (!botState.isConnected || !botState.bot) {
    return createNotConnectedResponse()
  }

  try {
    // Set pathfinder Movements
    const movements = new Movements(botState.bot)
    botState.bot.pathfinder.setMovements(movements)

    // Set target position
    const goal = new goals.GoalBlock(x, y, z)

    return new Promise<ToolResponse>((resolve) => {
      // Start movement
      botState
        .bot!.pathfinder.goto(goal)
        .then(() => {
          resolve(
            createSuccessResponse(
              `Successfully moved to X=${x}, Y=${y}, Z=${z}`
            )
          )
        })
        .catch((err) => {
          resolve(createErrorResponse(err))
        })

      // Timeout handling (if still moving after 1 minute)
      setTimeout(() => {
        resolve(
          createSuccessResponse(
            'Movement is taking longer than expected. Still trying to reach the destination...'
          )
        )
      }, 60000)
    })
  } catch (error) {
    return createErrorResponse(error)
  }
}
  • src/tools/movement.ts:41-45 (schema)
    Zod schema defining the input parameters for the moveTo tool: x, y, z coordinates as numbers.
    {
  x: z.number().describe('X coordinate'),
  y: z.number().describe('Y coordinate'),
  z: z.number().describe('Z coordinate'),
},
  • src/tools/movement.ts:38-87 (registration)
    Direct registration of the 'moveTo' tool via server.tool call within the registerMovementTools function.
    server.tool(
  'moveTo',
  'Move the player to a specific location',
  {
    x: z.number().describe('X coordinate'),
    y: z.number().describe('Y coordinate'),
    z: z.number().describe('Z coordinate'),
  },
  async ({ x, y, z }) => {
    if (!botState.isConnected || !botState.bot) {
      return createNotConnectedResponse()
    }

    try {
      // Set pathfinder Movements
      const movements = new Movements(botState.bot)
      botState.bot.pathfinder.setMovements(movements)

      // Set target position
      const goal = new goals.GoalBlock(x, y, z)

      return new Promise<ToolResponse>((resolve) => {
        // Start movement
        botState
          .bot!.pathfinder.goto(goal)
          .then(() => {
            resolve(
              createSuccessResponse(
                `Successfully moved to X=${x}, Y=${y}, Z=${z}`
              )
            )
          })
          .catch((err) => {
            resolve(createErrorResponse(err))
          })

        // Timeout handling (if still moving after 1 minute)
        setTimeout(() => {
          resolve(
            createSuccessResponse(
              'Movement is taking longer than expected. Still trying to reach the destination...'
            )
          )
        }, 60000)
      })
    } catch (error) {
      return createErrorResponse(error)
    }
  }
)

Tool Definition Quality

C2.9/5.0
Behavior2/5

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

With no annotations provided, the description carries full burden but offers minimal behavioral context. It states the action ('Move') but doesn't disclose whether this is instantaneous teleportation, requires specific permissions, has cooldowns, affects game state, or what happens if coordinates are invalid. For a mutation tool with zero annotation coverage, this is inadequate.

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 that directly states the tool's function without unnecessary words. It's appropriately sized and front-loaded with the core action.

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?

For a mutation tool with no annotations and no output schema, the description is incomplete. It doesn't explain what 'Move' entails behaviorally (e.g., teleportation vs. pathfinding), potential side effects, error conditions, or return values. Given the complexity of movement in a game context, more context is needed.

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%, with all three parameters (x, y, z) clearly documented as coordinates in the schema. The description adds no additional parameter information beyond implying coordinates are needed for 'specific location', which the schema already covers. Baseline 3 is appropriate when 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 action ('Move') and target ('the player') with a specific destination ('to a specific location'), which is a clear verb+resource combination. However, it doesn't differentiate from sibling tools like 'moveControl' or 'followEntity' that might involve movement in different ways.

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. It doesn't mention when teleportation-style movement is appropriate versus continuous movement tools like 'moveControl' or pathfinding tools, nor does it specify prerequisites or exclusions.

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/nacal/mcp-minecraft-remote'

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