Skip to main content
Glama

get-position

Retrieve the current coordinates of your Minecraft character to track location and enable precise navigation in the game world.

Instructions

Get the current position of the bot

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The handler function retrieves the bot's current entity position, floors the X, Y, Z coordinates, formats them into a string, and returns it via factory.createResponse.
    async () => {
      const bot = getBot();
      const position = bot.entity.position;
      const pos = {
        x: Math.floor(position.x),
        y: Math.floor(position.y),
        z: Math.floor(position.z)
      };
      return factory.createResponse(`Current position: (${pos.x}, ${pos.y}, ${pos.z})`);
    }
  • Registration of the "get-position" tool with factory.registerTool, including name, description, empty input schema, and inline handler function.
    factory.registerTool(
      "get-position",
      "Get the current position of the bot",
      {},
      async () => {
        const bot = getBot();
        const position = bot.entity.position;
        const pos = {
          x: Math.floor(position.x),
          y: Math.floor(position.y),
          z: Math.floor(position.z)
        };
        return factory.createResponse(`Current position: (${pos.x}, ${pos.y}, ${pos.z})`);
      }
    );
  • src/main.ts:51-51 (registration)
    Top-level call to registerPositionTools function, which registers the get-position tool among others.
    registerPositionTools(factory, getBot);
Behavior2/5

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

No annotations are provided, so the description carries full burden. While 'Get' implies a read operation, it doesn't disclose what format the position is returned in (coordinates, orientation), whether it's real-time or cached, or any limitations. The description adds minimal behavioral context beyond the basic operation.

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?

Perfectly concise at 5 words with zero waste. The description is front-loaded with the essential information and contains no 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?

For a tool with no annotations and no output schema, the description is insufficient. It doesn't explain what the position data includes (coordinates, orientation, dimension), the format of the return value, or any constraints. The agent would need to guess about the output structure.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With 0 parameters and 100% schema description coverage, the baseline is 4. The description appropriately doesn't waste space discussing non-existent parameters, though it could theoretically mention that no inputs are required.

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 ('Get') and resource ('current position of the bot'), making the purpose immediately understandable. However, it doesn't differentiate from siblings like 'move-to-position' or 'fly-to' which involve position manipulation rather than retrieval.

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 about when to use this tool versus alternatives. With siblings like 'move-to-position' and 'fly-to' that involve position-related actions, the description doesn't indicate this is purely for querying current location versus initiating movement.

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/yuniko-software/minecraft-mcp-server'

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