Skip to main content
Glama
leo4life2

Minecraft MCP Server

by leo4life2

hunt

Track and hunt specific animals or mobs in Minecraft using precise targeting options. Define the target type, name, quantity, and duration to complete hunting tasks efficiently.

Instructions

Hunt animals or mobs

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
amountNoNumber to hunt (default: 1)
durationNoMax duration in seconds (default: 60)
targetNameNoOptional: Specific name of the target
targetTypeYesType of target: 'animal' or 'mob'

Implementation Reference

  • Core handler function for the 'hunt' tool. Validates parameters and delegates to the 'attack' helper function with adjusted parameters for hunting.
    export const hunt = async (
      bot: Bot,
      params: ISkillParams,
      serviceParams: ISkillServiceParams,
    ): Promise<boolean> => {
      const skillName = 'hunt';
      const requiredParams: string[] = [];
      const isParamsValid = validateSkillParams(
        params,
        requiredParams,
        skillName,
      );
      if (!isParamsValid) {
        serviceParams.cancelExecution?.();
        bot.emit(
          'alteraBotEndObservation',
          `Mistake: You didn't provide all of the required parameters ${requiredParams.join(', ')} for the ${skillName} skill.`,
        );
        return false;
      }
      const unpackedParams = {
        targetType: params.targetType ?? '',
        targetName: params.targetName ?? null,
        amount: params.amount ?? 4,
        duration: params.duration ?? 30,
      };
    
      unpackedParams.duration = Math.min(unpackedParams.duration, 60);
      unpackedParams.amount = Math.min(unpackedParams.amount, 5);
      // amount and duration order is reversed for attack
      return attack(bot, {
        targetType: unpackedParams.targetType,
        targetName: unpackedParams.targetName,
        duration: unpackedParams.duration,
        killNumber: unpackedParams.amount,
        getStatsData: serviceParams.getStatsData,
        setStatsData: serviceParams.setStatsData,
        signal: serviceParams.signal,
        resetTimeout: serviceParams.resetTimeout,
      });
    };
  • Input schema definition for the 'hunt' tool, including description, parameters, and required fields.
    hunt: {
        description: "Hunt animals or mobs",
        params: {
            targetType: { type: "string", description: "Type of target: 'animal' or 'mob'" },
            targetName: { type: "string", description: "Optional: Specific name of the target" },
            amount: { type: "number", description: "Number to hunt (default: 1)" },
            duration: { type: "number", description: "Max duration in seconds (default: 60)" }
        },
        required: ["targetType"]
    },
  • Registers all skills (including 'hunt') as MCP tools by including them in the ListTools response.
        const skillTools = skillRegistry.getAllSkills().map(skill => ({
            name: skill.name,
            description: skill.description,
            inputSchema: skill.inputSchema
        }));
    
        return { tools: [...tools, ...skillTools] };
    });
  • Loads skills from skillRegistry (including 'hunt') and registers them in the SkillRegistry, making them available as tools.
    async function initializeSkills() {
        const skills = await loadSkills();
        for (const skill of skills) {
            skillRegistry.registerSkill(skill);
        }
    }
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. 'Hunt animals or mobs' implies an action with potential outcomes (e.g., resource gathering, combat), but it doesn't describe what happens during or after the hunt, such as success conditions, item drops, or risks. For a tool with no annotation coverage, this is inadequate.

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 extremely concise at three words, front-loaded with the core action. Every word earns its place by specifying the verb and target types, with no wasted text. This is efficient and easy to parse.

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 complexity of a hunting action with 4 parameters, no annotations, and no output schema, the description is incomplete. It fails to explain behavioral aspects, return values, or usage context, making it insufficient for an agent to fully understand the tool's operation 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?

The description adds no meaning beyond the input schema, which has 100% coverage with clear parameter descriptions (e.g., 'Number to hunt', 'Type of target'). Since the schema fully documents the parameters, the baseline score is 3, as the description doesn't compensate but also doesn't detract.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description 'Hunt animals or mobs' states the basic action and target types, which clarifies the tool's purpose. However, it's vague about the specific mechanics (e.g., hunting vs. attacking) and doesn't distinguish it from sibling tools like 'attackSomeone' or 'mineResource', which could involve similar actions on entities. It avoids tautology but lacks specificity.

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. It doesn't mention prerequisites, context (e.g., in-game environment), or exclusions, leaving the agent to infer usage from the name alone. With many sibling tools involving entity interaction, this lack of differentiation is a significant gap.

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

Related 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/leo4life2/minecraft-mcp-http'

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