Skip to main content
Glama

Set inventory slot

set_inventory_slot
DestructiveIdempotent

Places an item stack into a specific Minecraft inventory slot, replacing existing contents; use 'air' to empty a slot.

Instructions

Put an item stack into one inventory slot, replacing whatever was there.

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>",
      "slot": "<slot>",
      "item": "<item>"
    },
    "name": "set_inventory_slot"
  }
}

Input Schema

NameRequiredDescriptionDefault
itemYesItem id; use 'air' to empty the slot.
slotYesInventory slot: 0-8 hotbar, 9-35 main, 36 boots, 37 leggings, 38 chestplate, 39 helmet, 40 off-hand.
amountNoStack size.
usernameYesExact, case-sensitive name of an online player.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true, idempotentHint=true, and readOnlyHint=false, so the safety profile is known. The phrase 'replacing whatever was there' restates the overwrite consequence in concrete terms, which is mild added value, but it says nothing about whether the target player must be online, what happens on a failed write, or the response shape.

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 sentence with the action and the destructive consequence front-loaded. Nothing is wasted and nothing is buried.

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?

With a fully documented schema and an output schema present, the description only needs to convey intent and the overwrite behavior, which it does. It stops short of noting prerequisites such as the player being online or error behavior, but those gaps are minor at this complexity.

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 slot ranges, the 'air' empty-slot convention, amount bounds, and the online-player requirement are already documented in the schema. The description adds no parameter meaning beyond that, making the baseline 3 correct.

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?

States a specific verb (put) and resource (an item stack into one inventory slot), with the scope narrowed to a single slot. That implicitly separates it from whole-inventory siblings like clear_inventory and get_inventory, but no sibling is named explicitly.

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?

There is no when-to-use or when-not-to-use guidance, and no named alternative for related tasks (e.g., clearing a slot, setting entity equipment). The agent must infer from the tool name and the sibling list.

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