Skip to main content
Glama
leo4life2

Minecraft MCP Server

by leo4life2

buildSomething

Automate Minecraft structure creation using commands or dynamic JavaScript code. Use buildScript for predefined commands or code for custom, scripted building, enabling precise and scalable construction in-game.

Instructions

Build structures using Minecraft commands (requires cheats/operator permissions). Supports two modes: 1) buildScript - array of command objects like [{"command": "fill", "x1": 0, "y1": 64, "z1": 0, "x2": 10, "y2": 70, "z2": 10, "block": "stone"}], 2) code - JavaScript string for dynamic building like "for(let i = 0; i < 10; i++) { setBlock(pos.x + i, pos.y, pos.z, 'stone'); }"

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
buildScriptNoArray of build commands. Supported commands: setblock (place single block), fill (fill region), clone (copy region), summon (spawn entities), give (give items), raw (execute raw command). Each command is an object with command type and parameters.
codeNoJavaScript code string for dynamic building. Available functions: setBlock(x,y,z,block), fill(x1,y1,z1,x2,y2,z2,block,mode?), clone(x1,y1,z1,x2,y2,z2,dx,dy,dz,mode?), summon(entity,x?,y?,z?), give(item,count?), execute(command), wait(ticks), log(message). Variables: bot, pos (bot position), Math, shouldStop().
Behavior3/5

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

With no annotations provided, the description carries full burden. It discloses important behavioral traits: permission requirements ('requires cheats/operator permissions') and the two execution modes. However, it doesn't mention rate limits, error handling, whether operations are reversible, or what happens when both buildScript and code are provided.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is appropriately sized and front-loaded with the core purpose. Every sentence adds value: permission requirements, two modes, and examples. It could be slightly more structured with bullet points for the modes, but it remains efficient with no wasted words.

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?

Given 2 parameters with 100% schema coverage but no annotations or output schema, the description is moderately complete. It covers purpose, permissions, and modes with examples, but lacks information about return values, error cases, or how the tool behaves when both parameters are provided. For a tool with no output schema, more detail on expected outcomes would be helpful.

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?

Schema description coverage is 100%, so baseline is 3. The description adds significant value by explaining the two modes with concrete examples: 'buildScript - array of command objects' with a fill example, and 'code - JavaScript string for dynamic building' with a loop example. This clarifies the high-level semantics beyond the schema's detailed parameter documentation.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool's purpose: 'Build structures using Minecraft commands' with specific verbs ('build') and resources ('structures'). It distinguishes from siblings like 'buildPixelArt' by emphasizing general structure building rather than pixel art creation, and from 'placeItemNearYou' by focusing on command-based building at coordinates.

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 description provides clear context for when to use this tool: 'requires cheats/operator permissions' and supports two modes. However, it doesn't explicitly state when NOT to use it or name specific alternatives among siblings (e.g., when to use buildPixelArt vs. this tool).

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