Skip to main content
Glama

Clear inventory

clear_inventory
Destructive

Removes items from an online Minecraft player's inventory, either all items or one item type, and can limit how many items are removed.

Instructions

Remove items from an online player's inventory (all items, or only one item type).

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": {
      "username": "<username>"
    },
    "name": "clear_inventory"
  }
}

Input Schema

NameRequiredDescriptionDefault
itemNoOnly remove this item id; default: every item.
usernameYesExact, case-sensitive name of an online player.
max_countNoRemove at most this many items; default: all.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior3/5

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

The destructiveHint annotation already communicates the safety-critical behavior, and the description adds that the target player must be online and that removal can be scoped to one item type. It does not explain irreversibility, how partial failures are handled, or what happens when the player is offline.

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, front-loaded sentence with no wasted wording. The verb, target, and scope are all clear immediately.

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

Completeness4/5

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

Given the fully described input schema, destructive annotations, and the presence of an output schema, the description is largely complete for calling the tool correctly. The main minor gap is that it does not mention alternatives or deletion consequences beyond what the annotations already imply.

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 description coverage is 100%, so all three parameters are already documented in the schema itself. The description echoes the optional item scope but does not add meaningful semantics for username or max_count beyond what the schema provides.

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 uses a specific verb and resource: 'Remove items from an online player's inventory', and clarifies the scope as all items or only one item type. It does not explicitly differentiate itself from sibling tools such as get_inventory or set_inventory_slot, so it stops short of a 5.

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

Usage Guidelines3/5

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

The description implies the tool is used for inventory deletion and distinguishes between clearing everything or a single item type. However, it gives no explicit when-to-use guidance, prerequisites, or alternatives to consider before deleting inventory contents.

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