Skip to main content
Glama
zeeweebee

Minecraft MCP Server

by zeeweebee

get-block-info

Retrieve detailed information about blocks at specific coordinates in Minecraft, enabling players to identify materials and properties for building or exploration.

Instructions

Get information about a block at the specified position

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
xYesX coordinate
yYesY coordinate
zYesZ coordinate

Implementation Reference

  • The asynchronous handler function that executes the 'get-block-info' tool. It retrieves the block at the given (x,y,z) coordinates using bot.blockAt and returns information about the block including its name, type, and position.
    async ({ x, y, z }): Promise<McpResponse> => {
      try {
        const blockPos = new Vec3(x, y, z);
        const block = bot.blockAt(blockPos);
    
        if (!block) {
          return createResponse(`No block information found at position (${x}, ${y}, ${z})`);
        }
    
        return createResponse(`Found ${block.name} (type: ${block.type}) at position (${block.position.x}, ${block.position.y}, ${block.position.z})`);
      } catch (error) {
        return createErrorResponse(error as Error);
      }
    }
  • The input schema using Zod for validating the parameters x, y, z coordinates required by the 'get-block-info' tool.
    {
      x: z.number().describe("X coordinate"),
      y: z.number().describe("Y coordinate"),
      z: z.number().describe("Z coordinate"),
    },
  • src/bot.ts:438-460 (registration)
    The registration of the 'get-block-info' tool on the MCP server, including name, description, input schema, and inline handler function.
    server.tool(
      "get-block-info",
      "Get information about a block at the specified 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 {
          const blockPos = new Vec3(x, y, z);
          const block = bot.blockAt(blockPos);
    
          if (!block) {
            return createResponse(`No block information found at position (${x}, ${y}, ${z})`);
          }
    
          return createResponse(`Found ${block.name} (type: ${block.type}) at position (${block.position.x}, ${block.position.y}, ${block.position.z})`);
        } catch (error) {
          return createErrorResponse(error as Error);
        }
      }
    );
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states it 'gets information', implying a read-only operation, but doesn't specify what information is returned (e.g., block type, properties), whether it requires specific permissions, or if it has side effects like triggering events. This leaves significant gaps for a tool with no annotation coverage.

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 purpose without unnecessary words. It's front-loaded and earns its place by clearly conveying 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?

Given the complexity (a read operation with 3 parameters), lack of annotations, and no output schema, the description is incomplete. It doesn't explain what information is retrieved (e.g., block type, metadata) or the return format, leaving the agent uncertain about the tool's behavior and output.

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?

The schema description coverage is 100%, with clear descriptions for x, y, and z as coordinates. The description adds minimal value beyond the schema by mentioning 'at the specified position', which is implied by the parameters. This meets the baseline for high schema coverage.

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 information about') and resource ('a block'), making the purpose understandable. However, it doesn't differentiate from sibling tools like 'find-block' or 'detect-gamemode', which might have overlapping functionality in a Minecraft-like context, so it doesn't reach the highest score.

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 such as 'find-block' or 'list-inventory'. It lacks explicit context, prerequisites, or exclusions, leaving the agent to infer usage based on the tool name alone.

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