Skip to main content
Glama
Sign In
MCP Minecraft Remote

MCP Minecraft Remote

by nacal
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

craftItem

Craft items in Minecraft using available materials. Specify the item name and quantity to produce.

Instructions

Craft an item using available materials

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": "craftItem"
  }
}

Input Schema

NameRequiredDescriptionDefault
itemNameYesName of the item to craft
countNoNumber of items to craft

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.1/5.0
Behavior2/5

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

With no annotations, the description bears full burden for behavioral details. It fails to state what happens on failure (insufficient materials, invalid item), whether materials are consumed, or how success is indicated.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Extremely concise (7 words, single sentence). However, the structure could be improved by front-loading the core purpose, though it is already clear. No extra fluff.

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 no output schema and no behavioral disclosure, the description is incomplete. It does not explain return values, error conditions, or side effects like material consumption. For a simple tool, more detail would be helpful.

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 both parameters have basic descriptions. The tool description adds no additional meaning beyond what the schema provides, so baseline 3 is appropriate.

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 uses a specific verb ('craft') and resource ('item'), and the phrase 'using available materials' adds context. It distinguishes from sibling tools like 'getRecipes' by implying an action to produce an item.

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 (e.g., 'getRecipes' to discover recipes first). No mention of prerequisites like having materials or a crafting station.

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