minecraft-ai-mcp

drop_item

Discard specified items from Minecraft inventory by naming the item and optional count. Clears inventory space by removing unneeded resources.

Instructions

Drop items from inventory

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": {
      "itemName": "<itemName>"
    },
    "name": "drop_item"
  }
}

Input Schema

Name	Required	Description	Default
`count`	No	Number of items to drop (all if not specified)
`itemName`	Yes	Name of the item to drop

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Aug 2, 2026

TDQS

B3.1/5.0

Behavior2/5

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

With no annotations, the description must disclose behavioral implications. It only says 'drop items' without noting that dropping likely removes items permanently, whether they become unrecoverable, or whether there are restrictions (e.g., can't drop equipped items). This leaves important behavioral ambiguity.

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 one short, front-loaded sentence with no redundancy. While it lacks additional context, it is appropriately concise for a single-action tool with minimal parameters.

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 is simple, but the description covers only the literal action. It lacks any note on permanence, inventory side effects, or usage context. Given no output schema or annotations, the description carries the burden and is insufficient for confident use by an agent.

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% and both parameters have descriptions, including the default behavior for count ('all if not specified'). The tool description adds no additional parameter semantics beyond the schema, 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.

Purpose5/5

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

The description uses a specific verb 'drop' and identifies the resource 'items from inventory'. Among siblings like equip_item, use_item, and craft_item, this clearly differentiates as the discard action, leaving no ambiguity about its function.

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. The description only states what it does, without mentioning scenarios (e.g., freeing inventory space) or excluding cases. It does not reference any sibling tools or provide context for selection.

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