Minecraft MCP Server

Overview Schema Source Related Servers Discussions Admin

find-item

Locate a specific item in your Minecraft bot's inventory by name or type to manage resources and plan actions effectively.

Instructions

Find a specific item in the bot's inventory

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": {
      "nameOrType": "<nameOrType>"
    },
    "name": "find-item"
  }
}

Input Schema

Name	Required	Description	Default
`nameOrType`	Yes	Name or type of item to find

Implementation Reference

src/bot.ts:287-309 (registration)

Registration of the 'find-item' MCP tool including schema and handler in the registerInventoryTools function.

server.tool(
  "find-item",
  "Find a specific item in the bot's inventory",
  {
    nameOrType: z.string().describe("Name or type of item to find")
  },
  async ({ nameOrType }): Promise<McpResponse> => {
    try {
      const items = bot.inventory.items();
      const item = items.find((item: any) =>
        item.name.includes(nameOrType.toLowerCase())
      );

      if (item) {
        return createResponse(`Found ${item.count} ${item.name} in inventory (slot ${item.slot})`);
      } else {
        return createResponse(`Couldn't find any item matching '${nameOrType}' in inventory`);
      }
    } catch (error) {
      return createErrorResponse(error as Error);
    }
  }
);

src/bot.ts:293-308 (handler)

Handler function that searches the bot's inventory for an item matching the given nameOrType (case-insensitive), returns count, name, and slot if found, or a not-found message.

async ({ nameOrType }): Promise<McpResponse> => {
  try {
    const items = bot.inventory.items();
    const item = items.find((item: any) =>
      item.name.includes(nameOrType.toLowerCase())
    );

    if (item) {
      return createResponse(`Found ${item.count} ${item.name} in inventory (slot ${item.slot})`);
    } else {
      return createResponse(`Couldn't find any item matching '${nameOrType}' in inventory`);
    }
  } catch (error) {
    return createErrorResponse(error as Error);
  }
}

src/bot.ts:290-292 (schema)
Input schema defining the required 'nameOrType' parameter as a string for the item to search for.
```
{
  nameOrType: z.string().describe("Name or type of item to find")
},
```

Schema Changelog

Changes observed during successful MCP inspections.

First observedAug 15, 2025

TDQS

B3.4/5.0

Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It only states the tool's purpose without describing what happens on success/failure, what data is returned (e.g., slot, count), or whether the search is exact or partial. This leaves significant ambiguity for an agent.

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, focused sentence with no filler or repetition. It is concise and front-loaded, earning a high score for structure even though it omits some behavioral details.

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 the tool's simplicity (one parameter, no output schema, no annotations), the description is still incomplete. It lacks essential context about return values, search behavior, and error handling, which is especially important because the agent cannot infer these from the 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 schema covers 100% of the parameter with a clear description ('Name or type of item to find'). The tool description adds no additional meaning beyond the schema, so the baseline score of 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 uses the specific verb 'find' and clearly identifies the resource as 'a specific item in the bot's inventory'. This distinguishes it from sibling tools like list-inventory (which lists all items) and find-blocks-by-type/find-entity (which search in the world, not inventory).

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 a specific item is needed by name or type, but it does not explicitly contrast with list-inventory or other alternatives. No 'when to use' or 'when not to use' guidance is provided, so the context is implied rather than stated.

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

Deploy Server