craftpilot-mcp

by laur221

Overview Schema Source Related Servers Discussions Admin

Local

mc_hotbar

Select a Minecraft hotbar slot (0–8) to switch the active item or block during gameplay.

Instructions

Select a hotbar slot (0-8).

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": {
      "slot": "<slot>"
    },
    "name": "mc_hotbar"
  }
}

Input Schema

Name	Required	Description	Default
`slot`	Yes	Slot 0-8

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Nov 7, 2026

TDQS

B3.1/5.0

Behavior2/5

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

No annotations are provided and the description carries the full burden. It does not disclose that this mutates game state (changes the held item), whether the selection is instant, or what happens if the slot is empty, which matter for a game-input tool.

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 short sentence with zero preamble and the key constraint front-loaded. Nothing could be removed without losing information.

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 one-parameter tool with a fully documented schema, the description is minimally adequate. However, with no annotations and no output schema, it leaves the state-changing nature of the action unexplained.

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 defines the required integer slot with min 0 and max 8. The description only restates the range, adding no meaning beyond the schema; baseline 3 applies.

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 states a specific verb ('Select') and resource ('hotbar slot') with the valid range, so an agent knows exactly what action it performs. It does not distinguish itself from siblings like mc_inventory or mc_use, but the action itself is unambiguous.

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?

There is no guidance on when to select a hotbar slot versus using mc_inventory, mc_use, or mc_attack. The agent must infer that this changes the active item and should precede a use/attack action.

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