Skip to main content
Glama

Set mob target

set_entity_target
Idempotent

Make a mob attack a specific living entity by UUID, or clear its current target by omitting the target UUID.

Instructions

Make a mob attack a specific living entity, or clear its target.

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

Input Schema

NameRequiredDescriptionDefault
uuidYesEntity UUID, e.g. as returned by summon_entity or get_players.
target_uuidNoUUID of the living entity to attack; omit to clear the target.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare this is a non-readonly but non-destructive, idempotent, non-open-world mutation, so safety is largely covered. The description adds the meaningful constraint that the target must be a living entity, but says nothing about what happens if the subject is not a mob, whether the target persists, or how errors surface.

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?

A single tightly written sentence that front-loads the primary action and immediately covers the secondary clear-target mode. Nothing is redundant or buried.

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

Completeness3/5

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

The tool is simple (two params, output schema present, annotations covering safety and idempotency), so little prose is required. Still, the definition omits failure modes (non-mob subject, non-living target) and does not state whether targeting is one-shot or persistent, which are the remaining ambiguities an agent would face.

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%, with both uuid and target_uuid fully documented including the omit-to-clear semantics and the UUID pattern. The description's "specific living entity" phrasing aligns with the schema but adds no syntax or format detail beyond it, 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?

"Make a mob attack a specific living entity, or clear its target" states a concrete verb (make attack / clear) and resource (mob target), and the dual mode is spelled out. It is distinguishable from nearby siblings like damage_entity or set_entity_ai, though it doesn't name any alternative explicitly.

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?

The "or clear its target" clause effectively documents the two modes (supply target_uuid vs omit it), which is real usage guidance. However, there is no indication of when to prefer this over damage_entity or set_entity_ai, nor any preconditions such as the subject needing to be a mob.

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