Skip to main content
Glama
Sign In
minecraft-mcp

minecraft-mcp

by IotA-asce
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Swap hands

swap_hands

Swap the items in a player's main hand and off hand to change equipped tools or blocks quickly.

Instructions

Swap the items in the player's main hand and off hand.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "swap_hands"
  }
}

Input Schema

NameRequiredDescriptionDefault
playerNoOnline player name (defaults to the first online player)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.1/5.0
Behavior4/5

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

With no annotations provided, the description carries the full burden. It clearly states the state-changing effect (swapping items), which is sufficient given the simplicity of the operation. No hidden behaviors or side effects need disclosure.

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, concise sentence that fully communicates the action without unnecessary words or repetition.

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

Completeness5/5

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

The tool is a simple one-parameter action with no output schema. The description adequately covers what the tool does, and the schema handles parameter details, making the description complete for this level of complexity.

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 schema already includes a description for the 'player' parameter with default behavior. The tool description adds no additional parameter information beyond this, so the baseline of 3 applies given 100% schema coverage.

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 uses a specific verb ('Swap') and identifies the exact resource ('items in the player's main hand and off hand'). It clearly distinguishes this tool from siblings like 'equip_item' or 'drop_item'.

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?

There is no explicit guidance on when to use this tool versus alternatives, nor any exclusions. However, the action is simple and the intended use case (swapping items) is strongly implied. It does not mention alternatives or prerequisites.

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