Skip to main content
Glama

Set entity velocity

set_entity_velocity
Idempotent

Set an entity's velocity vector by UUID to push it or make it jump; use vy=1 for about a 7-block jump.

Instructions

Push an entity: set its velocity vector (e.g. vy=1 for a jump of about 7 blocks).

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>",
      "vx": "<vx>",
      "vy": "<vy>",
      "vz": "<vz>"
    },
    "name": "set_entity_velocity"
  }
}

Input Schema

NameRequiredDescriptionDefault
vxYesBlocks per tick (20 ticks per second), -10 to 10.
vyYesBlocks per tick (20 ticks per second), -10 to 10.
vzYesBlocks per tick (20 ticks per second), -10 to 10.
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.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds real context by giving a scale calibration ("vy=1 for a jump of about 7 blocks"), but says nothing about whether velocity decays over time, whether it applies to players, or how it interacts with gravity or existing motion.

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 sentence, front-loaded with the plain-language action before the technical detail, and the parenthetical example earns its place by giving scale. No filler or restated title.

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 full schema coverage, annotations, and an output schema present, the description covers what is needed to invoke the tool correctly. The remaining gap is behavioral: it does not mention that the impulse is transient or how it composes with other motion, which would matter for an in-world physics mutation.

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 states units (blocks per tick, 20 ticks/second) and the -10..10 range for every component. The description's only addition is the concrete vy=1 → ~7 block jump mapping, which is a useful intuition but marginal against an already complete schema.

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 specific verb and resource ("set its velocity vector") plus the colloquial framing "Push an entity," so the effect is unmistakable. It does not name a contrasting sibling such as teleport_entity or set_entity_rotation, which is the only thing keeping it from a 5.

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 word "Push" and the jump example imply a use case (applying continuous motion rather than repositioning), but there is no explicit when-to-use or when-not-to-use guidance. An agent must infer that this is the right tool versus teleport_entity on its own.

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