Skip to main content
Glama
zeeweebee

Minecraft MCP Server

by zeeweebee

jump

Make a Minecraft character jump to navigate obstacles, reach higher areas, or avoid hazards in the game world.

Instructions

Make the bot jump

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • src/bot.ts:214-228 (registration)
    Registration of the 'jump' tool, including name, description, empty schema, and inline handler function.
    server.tool(
      "jump",
      "Make the bot jump",
      {},
      async (): Promise<McpResponse> => {
        try {
          bot.setControlState('jump', true);
          setTimeout(() => bot.setControlState('jump', false), 250);
    
          return createResponse("Successfully jumped");
        } catch (error) {
          return createErrorResponse(error as Error);
        }
      }
    );
  • The handler function that executes the jump logic by setting the bot's jump control state to true for 250ms.
    async (): Promise<McpResponse> => {
      try {
        bot.setControlState('jump', true);
        setTimeout(() => bot.setControlState('jump', false), 250);
    
        return createResponse("Successfully jumped");
      } catch (error) {
        return createErrorResponse(error as Error);
      }
    }
  • Empty input schema for the 'jump' tool (no parameters required).
    {},
Behavior2/5

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

With no annotations, the description carries full burden but provides minimal behavioral information. It states the action but doesn't disclose what happens (e.g., jump height, duration, whether it's a one-time action or continuous, if it requires specific permissions or has side effects). This is inadequate for a tool with zero annotation coverage.

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 with 'Make the bot jump'—a single, clear sentence that front-loads the purpose without unnecessary words. Every word earns its place, making it efficient for an agent 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 lack of annotations and output schema, the description is incomplete. It doesn't explain what the jump entails (e.g., mechanics, outcome, or return values), leaving significant gaps for an agent to understand the tool's behavior in this Minecraft context.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool has 0 parameters with 100% schema description coverage, so no parameter documentation is needed. The description doesn't add parameter information, which is appropriate here, earning a baseline score of 4 for matching the schema's completeness.

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 'Make the bot jump' clearly states the action (verb 'jump') but doesn't specify what 'the bot' refers to in this Minecraft context, nor does it distinguish from sibling tools like 'fly-to' or 'move-in-direction'. It's vague about the exact nature of the jump action.

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 is provided on when to use this tool versus alternatives like 'fly-to' or 'move-to-position'. The description doesn't mention prerequisites (e.g., whether the bot needs to be on ground), context (e.g., for navigation or combat), or exclusions.

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