Skip to main content
Glama
zeeweebee

Minecraft MCP Server

by zeeweebee

look-at

Directs a Minecraft bot to face specific coordinates in the game world. Use this tool to orient the character toward a target location for navigation, building, or interaction.

Instructions

Make the bot look at a specific position

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
xYesX coordinate
yYesY coordinate
zYesZ coordinate

Implementation Reference

  • The handler function for the 'look-at' tool. It takes x, y, z coordinates and uses the mineflayer bot's lookAt method to direct the bot's gaze to that position, returning a success message or error.
    async ({ x, y, z }): Promise<McpResponse> => {
      try {
        await bot.lookAt(new Vec3(x, y, z), true);
    
        return createResponse(`Looking at position (${x}, ${y}, ${z})`);
      } catch (error) {
        return createErrorResponse(error as Error);
      }
    }
  • Zod schema defining the input parameters for the 'look-at' tool: numeric x, y, z coordinates.
    {
      x: z.number().describe("X coordinate"),
      y: z.number().describe("Y coordinate"),
      z: z.number().describe("Z coordinate"),
    },
  • src/bot.ts:195-212 (registration)
    The registration of the 'look-at' tool using McpServer's tool method within the registerPositionTools function, including name, description, schema, and handler.
    server.tool(
      "look-at",
      "Make the bot look at a specific position",
      {
        x: z.number().describe("X coordinate"),
        y: z.number().describe("Y coordinate"),
        z: z.number().describe("Z coordinate"),
      },
      async ({ x, y, z }): Promise<McpResponse> => {
        try {
          await bot.lookAt(new Vec3(x, y, z), true);
    
          return createResponse(`Looking at position (${x}, ${y}, ${z})`);
        } catch (error) {
          return createErrorResponse(error as Error);
        }
      }
    );
Behavior1/5

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

No annotations are provided, so the description carries full burden for behavioral disclosure. It only states the action without explaining effects (e.g., changes orientation, triggers events), permissions needed, rate limits, or error conditions. This leaves critical behavioral traits unspecified, making it inadequate for safe invocation.

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, direct sentence with zero wasted words. It front-loads the core action ('Make the bot look at') and target ('specific position'), making it efficient and easy to parse. Every word earns its place.

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 no annotations, no output schema, and a tool that likely involves behavioral effects (orientation change), the description is incomplete. It lacks details on what 'look at' entails, return values, or error handling. For a 3-parameter tool with potential side effects, this minimal description is insufficient.

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 clear parameter descriptions (X, Y, Z coordinates). The description adds no additional meaning beyond the schema, such as coordinate system details or units. Baseline 3 is appropriate as the schema handles parameter documentation adequately.

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 states the action ('look at') and target ('specific position'), which provides a basic purpose. However, it's vague about what 'look at' means in this context (e.g., visual focus, orientation change) and doesn't differentiate from siblings like 'get-position' or 'move-to-position'. It avoids tautology by not just repeating the name.

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. It doesn't mention prerequisites, context (e.g., in-game environment), or exclusions. The agent must infer usage from the name and parameters alone, which is insufficient for clear decision-making.

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