minecraft-mcp

Overview Schema Source Related Servers Discussions Admin

Set gamemode

set_gamemode

Switch a player's game mode among survival, creative, adventure, or spectator. Creative mode allows instant breaking and free placement.

Instructions

Change the player's gamemode (creative enables instant breaking and free placement).

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "mode": "<mode>"
    },
    "name": "set_gamemode"
  }
}

Input Schema

Name	Required	Description	Default
`mode`	Yes
`player`	No	Online player name (defaults to the first online player)

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Aug 7, 2026

TDQS

B3.3/5.0

Behavior2/5

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

With no annotations provided, the description carries the full burden. It states 'Change' and a creative-mode effect, but doesn't disclose permissions, reversibility, or effects on the specified player vs default. This is minimal disclosure 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?

A single sentence that is front-loaded with the action and includes a useful parenthetical. No wasted words.

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

Completeness3/5

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

For a simple two-parameter setter, the description is functional but sparse. It lacks behavioral transparency and alternative guidance, yet the schema and parenthetical cover essential invocation details. A middle score reflects the missing safety and usage contexts.

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

Parameters3/5

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

Schema covers the 'player' parameter with a description but leaves 'mode' undocumented. The description adds meaning for 'creative' but not for the other enum values. Given 50% schema coverage, the description only partially compensates for the parameter documentation gap.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Description uses the specific verb 'Change' with the resource 'player's gamemode', clearly distinguishing it from sibling tools like set_time or set_weather. The parenthetical adds concrete behavioral detail for creative mode, reinforcing the purpose.

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 when-to-use or alternative guidance is provided. The description merely states the action; it doesn't explain when to choose this over run_command or indicate exclusions. The creative-mode note is a behavioral detail rather than usage direction.

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