Skip to main content
Glama
leo4life2

Minecraft MCP Server

by leo4life2

goToKnownLocation

Direct an AI agent to specific coordinates in Minecraft using this tool. Input X, Y, and Z values to navigate to a precise location, with an optional name for reference. Ensures accurate in-game positioning.

Instructions

Navigate to specific coordinates

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameNoOptional: Name of the location
xYesX coordinate
yYesY coordinate
zYesZ coordinate

Implementation Reference

  • The main handler function that implements the goToKnownLocation tool logic. Validates parameters, navigates to coordinates using navigateToLocation or to a person using goToPerson.
    export const goToKnownLocation = async (
      bot: Bot,
      params: ISkillParams,
      serviceParams: ISkillServiceParams,
    ): Promise<boolean> => {
      const skillName = 'goToKnownLocation';
      const requiredParams = ['x', 'y', 'z'];
      const isParamsValid = validateSkillParams(
        params,
        requiredParams,
        skillName,
      );
      if (!isParamsValid) {
        serviceParams.cancelExecution?.();
        bot.emit(
          'alteraBotEndObservation',
          `Mistake: You didn't provide all of the required parameters ${requiredParams.join(', ')} for the ${skillName} skill.`,
        );
        return false;
      }
    
      const unpackedParams = {
        x: params.x,
        y: params.y,
        z: params.z,
        name: params.name,
        signal: serviceParams.signal,
      };
      const {x, y, z, name, signal} = unpackedParams;
    
      if (!name) {
        await navigateToLocation(bot, {
          x,
          y,
          z,
          signal,
          range: 1,
          verbose: true,
          allowTeleport: false,
        });
      } else {
        await goToPerson(bot, {
          name,
          distance: 3,
          keepFollowing: false,
          signal,
        });
      }
    };
  • Defines the input schema for the goToKnownLocation skill, including parameters, descriptions, and required fields. Used to register the skill dynamically.
    goToKnownLocation: {
        description: "Navigate to specific coordinates",
        params: {
            x: { type: "number", description: "X coordinate" },
            y: { type: "number", description: "Y coordinate" },
            z: { type: "number", description: "Z coordinate" },
            name: { type: "string", description: "Optional: Name of the location" }
        },
        required: ["x", "y", "z"]
    },
  • The SKILL_METADATA entry that registers the goToKnownLocation skill by providing its metadata for dynamic loading and execution.
    goToKnownLocation: {
        description: "Navigate to specific coordinates",
        params: {
            x: { type: "number", description: "X coordinate" },
            y: { type: "number", description: "Y coordinate" },
            z: { type: "number", description: "Z coordinate" },
            name: { type: "string", description: "Optional: Name of the location" }
        },
        required: ["x", "y", "z"]
    },
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 only states the basic action. It doesn't disclose behavioral traits such as whether navigation is instant or takes time, if it requires specific permissions or game states, what happens on failure (e.g., blocked path), or any side effects (e.g., consuming resources).

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 wasted words. It's front-loaded with the core action and target, making it immediately understandable 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?

For a tool with no annotations and no output schema, the description is incomplete. It doesn't explain what happens after navigation (e.g., success/failure response, time taken, state changes) or address the complexity of coordinate-based movement in a game context with potential obstacles or restrictions.

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 all parameters (x, y, z as coordinates, name as optional location identifier). The description adds no additional meaning beyond implying coordinate-based navigation, which is already clear from the parameter names. Baseline 3 is appropriate as 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 'Navigate to specific coordinates' clearly states the action (navigate) and target (specific coordinates), which distinguishes it from most siblings like 'goToSomeone' or 'lookAround'. However, it doesn't explicitly differentiate from all movement-related siblings like 'runAway' or 'swimToLand' in terms of coordinate-based vs. target-based navigation.

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 prerequisites (e.g., being in a game world), exclusions (e.g., not usable while sleeping), or comparisons to siblings like 'goToSomeone' (for entity-based movement) or 'runAway' (for fleeing).

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

Related 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/leo4life2/minecraft-mcp-http'

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