Minecraft MCP Server

by zeeweebee

Overview Schema Source Related Servers Discussions Admin

JavaScript

jump

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

Instructions

Make the bot jump

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "jump"
  }
}

Input Schema

Name	Required	Description	Default
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);
    }
  }
);

src/bot.ts:218-227 (handler)

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);
  }
}

src/bot.ts:217-217 (schema)
Empty input schema for the 'jump' tool (no parameters required).
```
{},
```

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedv1.0.0Jan 3, 2026
- removedInput schema / additionalProperties
```
Removed value: -false
```
First observedAug 15, 2025

TDQS

B3.3/5.0

Behavior2/5

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

With no annotations, the description carries the full burden of behavioral disclosure. It only states the action 'make the bot jump' and does not explain effects on movement, cooldowns, side effects, or requirements (e.g., being on ground). This is a significant gap for a mutation-like action.

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 clear sentence with no unnecessary words. It is highly concise and front-loaded, effectively communicating the core action.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's simplicity (no parameters, no output schema, no annotations), the description is adequate for an agent to invoke the action. However, it lacks situational context, such as typical use cases or potential constraints, which would enhance completeness in the broader environment.

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 zero parameters, so the schema is trivially 100% covered. The description adds no parameter information, but none is needed. Baseline for 0 params is 4.

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 'Make the bot jump' clearly identifies the action and resource (the bot). It is specific and distinct from siblings like goto or look_at, but does not explicitly differentiate itself from alternatives or provide comparative context.

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, nor any prerequisites or exclusions. The usage is implied by the action name itself but not elaborated, leaving the agent without situational context.

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

Deploy Server