Skip to main content
Glama

Mount or dismount

ride_entity
Idempotent

Makes one Minecraft entity ride another, such as a horse, boat, or minecart, or dismounts it when no vehicle UUID is provided.

Instructions

Make one entity ride another, or dismount 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": {
      "passenger_uuid": "<passenger_uuid>"
    },
    "name": "ride_entity"
  }
}

Input Schema

NameRequiredDescriptionDefault
vehicle_uuidNoEntity to ride (horse, boat, minecart, pig, another mob...); omit to dismount.
passenger_uuidYesEntity that rides.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.3/5.0
Behavior2/5

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

Annotations already declare this is a non-read-only, idempotent, non-destructive, closed-world mutation, so the description's restatement of the title adds essentially nothing behavioral. It does not say what happens on an invalid or duplicate mount, whether an existing vehicle link is replaced, or what error/result to expect.

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 front-loaded sentence with zero filler that communicates both operating modes. Nothing is padded and nothing essential is 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?

Return values need not be explained because an output schema exists, and both parameters are fully documented. However, for a two-mode mutation tool with no exclusions or failure semantics in the description, an agent still lacks guidance on edge cases such as dismounting an unmounted passenger.

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%: vehicle_uuid is documented as the entity to ride with 'omit to dismount', and passenger_uuid as the rider, far richer than anything the description provides. The description adds no additional meaning, so the baseline 3 is correct.

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 concrete verb+resource pair (mount/dismount a passenger onto/off a vehicle entity) and clarifies a dual-mode tool whose name alone ("ride_entity") would leave the dismount half ambiguous. It is not differentiated from siblings, but no sibling in the list offers comparable mount behavior, so that gap is minor.

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 agent must infer from the schema's vehicle_uuid note ('omit to dismount') that mounting and dismounting are the two modes. There is no explicit when-to-use versus alternatives (e.g., teleport_entity) or stated preconditions such as the passenger already being mounted or the vehicle being rideable.

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