Skip to main content
Glama
Sign In
MCP Minecraft Remote

MCP Minecraft Remote

by nacal
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

equipItem

Equip a specified item from inventory to your hand or an armor slot like head, torso, legs, or feet.

Instructions

Equip an item from inventory to hand or armor slot

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": {
      "itemName": "<itemName>"
    },
    "name": "equipItem"
  }
}

Input Schema

NameRequiredDescriptionDefault
itemNameYesName of the item to equip
destinationNoSlot to equip the item tohand

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior2/5

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

With no annotations, the description must disclose behavioral traits, but it only states the basic function. It omits details like what happens if the item is not found, if the slot is occupied, or inventory state changes.

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 single-sentence description is concise and front-loaded with the core action, with no unnecessary words.

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?

For a simple tool, the description is adequate but lacks details on success/failure conditions and does not compensate for the absence of an output schema or annotations.

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 already provides full descriptions for both parameters (itemName and destination), and the description adds no additional semantic value beyond what the schema offers, resulting in a baseline score.

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 clearly specifies the action (equip), the resource (item from inventory), and the destination (hand or armor slot). It effectively distinguishes from sibling tools like checkInventory and tossItem.

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 description implies usage when equipping items but lacks explicit guidance on when not to use it, prerequisites (e.g., item must be in inventory), or alternatives.

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

Deploy Server

Other Tools