MCP Minecraft Remote

by nacal

Overview Schema Source Related Servers Discussions Admin

TypeScript

Remote

useOnEntity

Apply your held item to a target entity in Minecraft for actions such as feeding, shearing, or attacking.

Instructions

Use held item on a specific entity

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": {
      "entityId": "<entityId>"
    },
    "name": "useOnEntity"
  }
}

Input Schema

Name	Required	Description	Default
`entityId`	Yes	ID of the entity to use item on

Schema Changelog

Changes observed during successful MCP inspections.

First observedAug 18, 2025

TDQS

B3/5.0

Behavior1/5

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

No annotations are provided, and the description does not disclose behavioral traits such as whether the action is destructive, requires line of sight, or has cooldowns. The description fails to communicate what 'use' entails beyond the basic action.

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?

The description is a single, front-loaded sentence with no extraneous information. Every word serves a purpose.

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

Completeness2/5

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

Given the simplicity of the tool (one param, no output schema), the description lacks context about prerequisites, side effects, or return behavior, making it insufficient for an agent to fully understand when and how to invoke the tool.

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?

The input schema has one parameter (entityId) with a clear description. Since schema description coverage is 100%, the description does not need to add much; however, it merely restates the action without adding meaning beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description 'Use held item on a specific entity' clearly states the action (use) and the target (specific entity), distinguishing it from sibling tools like attackEntity or equipItem.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance on when to use this tool versus alternatives like attackEntity or interactWithEntity (if exists). No exclusions or context provided.

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