Skip to main content
Glama

Set entity rotation

set_entity_rotation
Idempotent

Rotates a Minecraft entity in place to a specified yaw and pitch without changing its position.

Instructions

Turn an entity to face a direction without moving 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>",
      "yaw": "<yaw>",
      "pitch": "<pitch>"
    },
    "name": "set_entity_rotation"
  }
}

Input Schema

NameRequiredDescriptionDefault
yawYesHorizontal facing in degrees: 0 = south, 90 = west, 180 = north, 270 (or -90) = east.
uuidYesEntity UUID, e.g. as returned by summon_entity or get_players.
pitchYesVertical facing in degrees: -90 = straight up, 0 = level, 90 = straight down.

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 the full safety profile (readOnly=false, idempotent=true, destructive=false, openWorld=false), so the bar is lower. The description adds one useful behavioral fact beyond them: the entity's position is unchanged. It says nothing about whether the change persists across reloads, applies immediately on the client, or fails for certain entity types.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single short sentence with no filler, and the key constraint ('without moving it') is placed where it will be read. It is arguably too terse to be a model of front-loading, but every word earns its place.

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?

This is a simple three-parameter mutation with an output schema and near-complete annotation coverage, so the description does not need to explain return values. The only meaningful gap is the absence of any guidance on failure modes or entity preconditions, which is minor for an operation of this simplicity.

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 yaw/pitch fields include precise degree mappings and even a UUID provenance hint, so the schema carries parameter meaning fully. The description adds no parameter-level detail, which is the expected baseline when the schema is this rich.

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?

States a specific verb and resource: 'turn an entity to face a direction.' The clause 'without moving it' implicitly distinguishes this from teleport_entity in the sibling set, though that sibling is not named explicitly. An agent can identify the operation, but the differentiation depends on inference.

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 phrase 'without moving it' implies the tool is for orientation-only changes and hints that teleport_entity is the alternative for position changes, but no explicit when-to-use or when-not-to-use guidance is given. There are no stated prerequisites (e.g., the entity must be loaded or online).

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