Skip to main content
Glama

Kill entities

kill_entities
DestructiveIdempotent

Remove up to 1,000 entities from the Minecraft main world by type, player name, or all non-player entities. Mobs vanish without drops; players die normally and drop items.

Instructions

Remove entities from the main world (at most 1,000 per call). Mobs are removed without drops; a killed player dies normally and drops their items. 'all' removes EVERY non-player entity, including pets, villagers, item frames, armor stands, paintings, boats and minecarts: prefer a specific type, or remove_entity for one entity.

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": {
      "target": "<target>"
    },
    "name": "kill_entities"
  }
}

Input Schema

NameRequiredDescriptionDefault
targetYesAn entity type such as 'zombie', 'player:<name>' to kill one player, or 'all'.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.7/5.0
Behavior4/5

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

Annotations already flag destructive=true and idempotent=true, yet the description adds genuinely non-obvious consequences: mobs vanish without drops while players die normally and drop items, and the per-call cap is disclosed. It stops short of saying whether the operation is reversible or what happens to entities in unloaded chunks, so it is not a full behavioral account.

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 scope and cap are front-loaded, then consequences, then the 'all' warning, then the alternative. Every clause carries information an agent needs; there is no filler or restatement of the title.

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

Completeness5/5

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

An output schema exists, so return values need not be explained, and with a single well-covered parameter the description has room to focus on risk and routing, which it does. Nothing needed to invoke this destructive tool safely is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the schema already defines 'target' and its pattern, but the description adds real meaning: the concrete consequences of 'all' (pets, villagers, item frames, armor stands, paintings, boats, minecarts) and the per-call ceiling that the schema does not express. That said, it does not clarify case sensitivity, wildcard support, or behavior when the target type matches nothing.

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?

States a specific verb (remove) and resource (entities) plus scope ('from the main world') and a hard limit ('at most 1,000 per call'). It also distinguishes itself from the sibling remove_entity by name, so an agent can choose between them without opening either schema.

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

Usage Guidelines5/5

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

Gives explicit routing guidance: prefer a specific type over 'all', and use remove_entity for a single entity. It also names the condition that makes the broad option risky ('all' removes EVERY non-player entity) rather than just describing the tool.

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