Skip to main content
Glama

Damage entity

damage_entity
Destructive

Deals health-point damage to a living Minecraft entity by UUID; enough damage kills it, and an optional source UUID assigns aggro and kill credit.

Instructions

Hurt a living entity. Enough damage kills it.

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>",
      "amount": "<amount>"
    },
    "name": "damage_entity"
  }
}

Input Schema

NameRequiredDescriptionDefault
uuidYesEntity UUID, e.g. as returned by summon_entity or get_players.
amountYesDamage in health points (2 = one heart).
source_uuidNoEntity to blame for the damage (affects aggro and kill credit).

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true, readOnlyHint=false, and non-idempotency, so the safety profile is covered. The description adds the meaningful outcome detail that accumulated damage can kill, but says nothing about death handling, invulnerable targets, or whether damage is clamped to remaining health.

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 short sentences, both front-loaded with the action and the consequence, and neither is redundant. Nothing extraneous is present.

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 an output schema present and annotations covering destructiveness, the description only needs to convey the core effect and its lethal consequence, which it does. Minor omissions remain around edge cases like player targets or damage immunity, but nothing critical for correct invocation is missing.

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 schema already explains UUID sources, the health-point/heart conversion, the 1,000,000 cap, and that source_uuid drives aggro and kill credit. The description adds no parameter-level meaning, 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?

"Hurt a living entity" gives a specific verb and a scoped resource (living entities only), and "enough damage kills it" clarifies the outcome. It stops short of naming a sibling such as remove_entity or apply_effect to disambiguate instant removal versus incremental damage.

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 only implied: the tool is for inflicting damage on living entities, and the note that sufficient damage kills implies a gradual-damage use case distinct from outright removal. There is no explicit when-to-use, when-not-to-use, or alternative recommendation.

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