Skip to main content
Glama

Drop loot

spawn_loot

Rolls a loot table once and drops the resulting items at a specified position in the main world, placing spawned loot exactly where you choose.

Instructions

Roll a loot table once and drop the resulting items at a position in the main world.

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": {
      "loot_table": "<loot_table>",
      "x": "<x>",
      "y": "<y>",
      "z": "<z>"
    },
    "name": "spawn_loot"
  }
}

Input Schema

NameRequiredDescriptionDefault
xYesExact X; block centres are at .5 (e.g. 100.5).
yYesExact Y of the feet.
zYesExact Z; block centres are at .5 (e.g. -20.5).
loot_tableYesLoot table id such as 'chests/simple_dungeon' or 'minecraft:entities/zombie'.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already indicate a non-read-only, non-destructive, non-idempotent operation. The description adds useful behavioral detail by specifying that the loot table is rolled once and that items are dropped at a position in the main world, although it does not describe edge cases such as missing loot tables or failure behavior.

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, efficiently structured sentence with no unnecessary wording. It front-loads the core behavior and position scope clearly.

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 tool has four required parameters, complete schema descriptions, annotations, and an output schema, so the description does not need to explain return values. It is nearly complete, though it could mention constraints such as loot table existence or world limitations more explicitly.

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 the input schema already documents the loot_table, x, y, and z parameters in detail. The description does not add parameter-specific meaning beyond the schema, which is acceptable given the complete schema coverage.

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 states a specific action and resource: it rolls a loot table once and drops the resulting items at a position in the main world. This is clear and specific, though it does not explicitly differentiate itself from sibling tools such as spawn_particles or other spawning tools.

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?

The description provides little guidance about when to use this tool versus alternatives. It implies usage by saying a loot table is rolled once and items are dropped in the main world, but it offers no explicit when-to-use or when-not-to-use conditions.

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