mcp-minecraft

move-to-position

Move a Minecraft bot to a specified position by providing X, Y, Z coordinates. Optionally, set how close to get (range) and a timeout to stop if the destination is unreachable.

Instructions

Move the bot to a specific position

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": {
      "x": "<x>",
      "y": "<y>",
      "z": "<z>"
    },
    "name": "move-to-position"
  }
}

Input Schema

Name	Required	Description
`x`	Yes	X coordinate
`y`	Yes	Y coordinate
`z`	Yes	Z coordinate
`range`	No	How close to get to the target (default: 1)
`timeoutMs`	No	Timeout in milliseconds before cancelling (min: 50, default: no timeout)

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedv2.0.2May 1, 2026

addedInput schema / properties / timeoutMs

Added value: +{
+  "description": "Timeout in milliseconds before cancelling (min: 50, default: no timeout)",
+  "minimum": 50,
+  "type": "integer"
+}

First observedAug 18, 2025

TDQS

C2.8/5.0

Behavior2/5

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

No behavioral details beyond a generic move action. Lacks information on collision handling, pathfinding, blocking behavior, or whether the bot stops exactly at the position. No annotations provided to compensate.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single sentence that is clear but very brief. It conveys the purpose without extra words, but could be more informative without becoming overly long.

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 movement tool with no output schema and no annotations, the description lacks essential details like whether the tool blocks, handles obstacles, or how timeout interacts with movement. Incomplete for an AI agent to anticipate behavior.

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 descriptions cover all parameters adequately (100% coverage). The description adds no extra meaning beyond what the schema provides, so baseline 3 is appropriate.

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 tool moves the bot to a specific position using coordinates. It distinguishes from siblings like fly-to or move-in-direction by the explicit mention of position, but could be more specific about the movement type.

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 on when to use this tool versus alternatives like fly-to or move-in-direction. No prerequisites or conditions for usage are mentioned.

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