MCP Minecraft Remote

by nacal

Overview Schema Source Related Servers Discussions Admin

TypeScript

Remote

openContainer

Open a container at specified coordinates to access its inventory and manage items remotely.

Instructions

Open a container (chest, furnace, etc.) at specific coordinates

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

Input Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

First observedAug 18, 2025

TDQS

B3.2/5.0

Behavior2/5

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

The description only says 'open', but does not disclose what happens when opening (e.g., whether it returns container contents, requires player to be near, or if opening a locked container fails). With no annotations provided, the description should cover these behaviors.

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?

One short, direct sentence. No wasted words.

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?

The tool has no output schema and interacts with game state. The description lacks details on return values, side effects, or what constitutes successful opening. For a tool that likely affects the game world, more context is needed.

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 coverage is 100% with descriptions for each coordinate, but the descriptions are trivial ('X coordinate...'). The description adds no extra meaning beyond the parameter names and schema.

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 action ('Open'), the resource ('container'), and provides examples ('chest, furnace, etc.'). It distinguishes this tool from siblings like closeContainer, checkInventory, etc.

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 on when to use this tool versus alternatives (e.g., when to use openContainer vs. useOnEntity for opening). No mention of prerequisites or context.

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