Skip to main content
Glama
zeeweebee

Minecraft MCP Server

by zeeweebee

detect-gamemode

Identify the current game mode in Minecraft to enable appropriate AI-controlled actions and interactions within the game world.

Instructions

Detect the gamemode on game

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The handler function for the 'detect-gamemode' tool. It returns the current game mode of the bot by accessing bot.game.gameMode.
    async (): Promise<McpResponse> => {
      try {
        return createResponse(`Bot gamemode: "${bot.game.gameMode}"`);
      } catch (error) {
        return createErrorResponse(error as Error);
      }
    }
  • src/bot.ts:634-646 (registration)
    The registration of the 'detect-gamemode' tool using server.tool() with an empty input schema and inline handler function.
      server.tool(
        "detect-gamemode",
        "Detect the gamemode on game",
        {},
        async (): Promise<McpResponse> => {
          try {
            return createResponse(`Bot gamemode: "${bot.game.gameMode}"`);
          } catch (error) {
            return createErrorResponse(error as Error);
          }
        }
      );
    }
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. It states the action ('detect') but doesn't disclose behavioral traits like whether this is a read-only operation, what permissions are needed, or how the detection works. This is inadequate for a tool with no 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.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, efficient sentence with no wasted words. However, it could be more front-loaded with clarity, as 'on game' is ambiguous, slightly reducing its effectiveness.

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 vague purpose, the description is incomplete. It doesn't explain what 'gamemode' means, what the detection returns, or how it interacts with the game context, making it insufficient for effective use.

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 information is needed. The description doesn't add param details, which is appropriate, earning a baseline score of 4 for this dimension.

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 states the tool's purpose ('detect the gamemode') and specifies the domain ('on game'), which is clear but vague. It doesn't distinguish from siblings like 'get-position' or 'list-inventory', and the phrase 'on game' is ambiguous about what exactly is being detected.

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. It doesn't mention prerequisites, context, or exclusions, leaving the agent to infer usage from the name alone.

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