mcp-minecraft

detect-gamemode

Identify the player's current game mode in Minecraft to enable appropriate behavior based on survival, creative, adventure, or spectator mode.

Instructions

Detect the gamemode on game

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": "detect-gamemode"
  }
}

Input Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

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

TDQS

B3/5.0

Behavior2/5

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

No annotations provided, so the description must fully disclose behavior. It only states 'detect', implying a read operation, but fails to mention side effects, permissions, or what exactly is returned (e.g., gamemode name or ID). Minimal disclosure.

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 extremely concise (4 words) with no wasted text. However, it lacks any structured formatting or front-loading of key information, but for a simple parameterless tool, brevity is acceptable.

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?

With no output schema and no annotations, the description is incomplete. The agent receives no information about what the tool returns (e.g., a string, number, or object). A detect tool should indicate the return value format for proper usage.

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 input schema has zero parameters, so schema description coverage is effectively 100%. The description adds no parameter semantics, but none are needed. Baseline of 4 is appropriate as the schema already captures all.

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 clearly states the tool detects the gamemode on a game. The verb 'detect' and resource 'gamemode' are specific. It is distinct from sibling tools like 'get-block-info' or 'list-inventory', but does not elaborate on what gamemode entails.

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 on when to use or when not to use this tool. There are no alternatives mentioned, and no context about prerequisites or scenarios where detection is appropriate.

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