Skip to main content
Glama
zeeweebee

Minecraft MCP Server

by zeeweebee

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

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameOrTypeYesName 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);
        }
      }
    );
  • 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);
      }
    }
  • 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")
    },
Behavior2/5

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

No annotations are provided, so the description carries full burden. It states it 'finds' an item but doesn't disclose behavioral traits like whether it returns the first match, all matches, error handling if not found, or if it requires the bot to have inventory access. This leaves significant gaps for a tool with mutation potential.

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, efficient sentence with zero waste. It's front-loaded with the core purpose and appropriately sized for a simple tool.

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 annotations, no output schema, and a simple input schema, the description is incomplete. It doesn't explain what 'find' means operationally (e.g., returns item details, location in inventory, or just existence), leaving the agent uncertain about behavior and outcomes.

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 the schema already documents the single parameter 'nameOrType' as 'Name or type of item to find'. The description doesn't add meaning beyond this, such as examples or clarification on 'type' versus 'name'. Baseline 3 is appropriate when schema does the heavy lifting.

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 clearly states the action ('find') and target ('specific item in the bot's inventory'), making the purpose understandable. However, it doesn't explicitly differentiate from sibling tools like 'list-inventory' or 'find-block', which would be needed for a perfect score.

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?

The description provides no guidance on when to use this tool versus alternatives like 'list-inventory' (which might list all items) or 'find-block' (which searches in the world). There's no mention of prerequisites, context, or exclusions for usage.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/zeeweebee/mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server