Skip to main content
Glama

jump

Control a Minecraft character to jump in real-time, enabling movement and interaction within the game world through AI commands.

Instructions

Make the bot jump

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Handler function for the "jump" tool. It sets the bot's jump control state to true, then false after 250ms, and returns a success response.
    async () => {
      const bot = getBot();
      bot.setControlState('jump', true);
      setTimeout(() => bot.setControlState('jump', false), 250);
      return factory.createResponse("Successfully jumped");
    }
  • Schema for the "jump" tool, which is empty indicating no input parameters are required.
    {},
  • Registration of the "jump" MCP tool using factory.registerTool, including name, description, schema, and handler.
    factory.registerTool(
      "jump",
      "Make the bot jump",
      {},
      async () => {
        const bot = getBot();
        bot.setControlState('jump', true);
        setTimeout(() => bot.setControlState('jump', false), 250);
        return factory.createResponse("Successfully jumped");
      }
    );
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. 'Make the bot jump' implies an action but doesn't disclose behavioral traits like whether this is instantaneous, has cooldowns, requires specific permissions, affects game state, or what happens on failure. It's minimal without essential context for a mutation tool.

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 a single three-word sentence that directly states the action. It's front-loaded with zero wasted words, making it efficient for quick understanding.

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 likely performs an action (jumping) with no annotations, no output schema, and minimal description, it's incomplete. The description doesn't cover what the jump does, potential outcomes, error conditions, or how it integrates with sibling tools like movement commands, leaving significant gaps for an agent.

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 semantics, but this is appropriate given the lack of parameters, meeting the baseline for tools with no parameters.

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 (make jump) but is vague about what 'the bot' refers to and lacks specificity about the execution context. It distinguishes from siblings like 'fly-to' or 'move-to-position' by focusing on jumping, but doesn't specify whether this is a physical jump in a game world or metaphorical 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 about when to use this tool versus alternatives. The description doesn't mention prerequisites (e.g., requires the bot to be on ground), exclusions (e.g., can't jump while flying), or suggest sibling tools for related actions like movement or navigation.

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/yuniko-software/minecraft-mcp-server'

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