mcp-minecraft

list-recipes

List all crafting recipes possible with current inventory. Optionally filter by desired output item name to see if the bot can craft it.

Instructions

List all available crafting recipes the bot can make with current inventory

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": "list-recipes"
  }
}

Input Schema

Name	Required	Description	Default
`outputItem`	No	Optional: filter recipes by output item name

Schema Changelog

Changes observed during successful MCP inspections.

Addedv2.0.2May 1, 2026

TDQS

A3.8/5.0

Behavior3/5

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

With no annotations provided, the description carries full burden. It states the tool lists recipes 'with current inventory', implying real-time filtering, but does not disclose any behavioral traits like idempotency, performance, or side effects. It is adequate but not rich.

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?

Single concise sentence of 10 words with no unnecessary information. Front-loaded with the core action and resource.

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

Completeness4/5

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

For a simple list tool with one optional parameter and no output schema, the description adequately covers what the tool does and the condition (current inventory). It does not explain return format, but that is inferable.

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%, so baseline is 3. The description does not add any parameter-specific information beyond what the schema already provides for the 'outputItem' parameter.

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 states the verb 'list' and the resource 'crafting recipes the bot can make with current inventory', which is specific and distinguishes it from siblings like 'get-recipe' and 'craft-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?

The description implies that this tool is for listing recipes the bot can currently make, but it does not explicitly state when to use it versus alternatives like 'can-craft' or 'get-recipe'. No guidance on when not to use or comparisons to siblings.

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