minecraft-ai-mcp

activate_block

Activate a block at specified coordinates to open chests, press buttons, and trigger in-game interactions.

Instructions

Activate/interact with a block (like opening a chest, pressing a button)

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": "activate_block"
  }
}

Input Schema

Name	Required	Description
`x`	Yes	X coordinate of the block
`y`	Yes	Y coordinate of the block
`z`	Yes	Z coordinate of the block

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Aug 2, 2026

TDQS

A3.5/5.0

Behavior2/5

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

With no annotations provided, the description carries full responsibility for behavioral disclosure. It only states the action without mentioning any side effects (e.g., changing block state), prerequisites (like proximity), or return feedback. This leaves significant behavioral gaps.

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, well-crafted sentence that uses concrete examples to clarify meaning without any wasted words. It is appropriately brief and front-loaded.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple tool with fully documented parameters, the description adequately explains the core purpose and usage context. However, it omits details about return values, prerequisites, or potential side effects, which is notable given the lack of an output schema and annotations.

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 input schema fully documents all three parameters with coordinate descriptions (100% coverage). The tool description adds no additional parameter-specific meaning, so the baseline score of 3 applies.

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 identifies the tool as activating or interacting with a block, with concrete examples (opening a chest, pressing a button). This distinguishes it from sibling tools like dig_block or place_block, though the word 'interact' is somewhat broad and could overlap with other actions.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The examples provide clear context for when to use the tool (e.g., opening a chest, pressing a button), implying typical interactive-block scenarios. However, it does not explicitly mention alternative tools or when not to use it, so it falls short of a perfect score.

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