Skip to main content
Glama

Remove entity

remove_entity
DestructiveIdempotent

Delete a single non-player Minecraft entity by UUID without item drops or a death animation. Use it to remove a specific mob or entity from the server.

Instructions

Delete one entity (not a player) without drops or death animation.

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": {
      "uuid": "<uuid>"
    },
    "name": "remove_entity"
  }
}

Input Schema

NameRequiredDescriptionDefault
uuidYesEntity UUID, e.g. as returned by summon_entity or get_players.

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 declare destructiveHint=true and idempotentHint=true, so the mutation profile is known. The description adds genuinely new behavioral context by specifying no item drops and no death animation, which affects observable world state. It stops short of saying what happens when the UUID does not exist or whether removal is reversible outside of idempotency.

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 sentence, front-loaded with the action and scope, with the target restriction and the side-effect caveat appended in priority order. No filler wording.

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?

An output schema exists and annotations cover the safety profile, so return values and destructiveness need no restatement. The description is nearly complete for a one-parameter mutation tool; the only real omission is what an agent should do instead for players, since the tool states the exclusion without routing elsewhere.

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% and the single uuid parameter is fully documented in the schema, including format and provenance from summon_entity or get_players. The description contributes no additional meaning about the identifier, so the baseline of 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 precise verb and resource ('Delete one entity'), constrains cardinality ('one'), and draws a boundary ('not a player'). The phrase 'without drops or death animation' implicitly separates it from damage_entity or a kill-style operation, though no sibling is named outright.

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?

A partial exclusion is present: the tool is for entities and explicitly not players, which steers an agent away from invalid targets. However, there is no statement of when to prefer this over damage_entity, nor guidance on what to do for players, leaving the alternative path implied.

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