Skip to main content
Glama

Get inventory

get_inventory
Read-onlyIdempotent

Retrieve a Minecraft online player's non-empty inventory slots, including item, amount, and enchantments, with optional filtering by specific slot numbers.

Instructions

List the non-empty inventory slots of an online player, with item, amount and enchantments. Slots: 0-8 hotbar, 9-35 main, 36 boots, 37 leggings, 38 chestplate, 39 helmet, 40 off-hand.

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

Input Schema

NameRequiredDescriptionDefault
slotsNoSlots to read; default: all 41 slots.
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

A3.8/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), so the description only needs to add context. It does: it discloses that only non-empty slots are returned and that the target must be an online player, both of which change what an agent should expect from a call. It does not say whether an offline player yields an error or an empty result, which keeps it out of 5 territory.

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?

Two compact lines: the first states what is returned, the second supplies the slot index legend. The key scope qualifier ('non-empty', 'online player') is front-loaded, and there is no filler.

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?

The description is complete relative to the tool's complexity: an output schema exists, so return values need not be explained, and the description covers the filtering behavior and the online-player prerequisite. The only real gap is error behavior when the player is not online, which is minor for a two-parameter read tool.

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 the schema already documents the slot numbering map (0-8 hotbar, 36-40 armor, 40 off-hand) inside the items description, so the description's slot legend largely repeats structured data. It adds no new meaning for the slots parameter, such as whether order matters or how duplicates are handled, so the baseline 3 applies.

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 gives a specific verb and resource: list the non-empty inventory slots of an online player, returning item, amount, and enchantments. This clearly separates it from mutation siblings such as clear_inventory and set_inventory_slot, but it never names or contrasts those siblings, and it leaves the agent to infer the difference.

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?

Usage is implied rather than stated: 'of an online player' establishes a prerequisite (the target must be online) and 'non-empty' implies that the description of the read operation is scoped. There is no explicit when-to-use guidance, no exclusion of alternatives like get_entity_equipment, and no mention of what happens if the player is offline.

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